14 Sep, 2006
1 commit
-
The ethtool_ops structure is immutable, it expected to be setup
by the driver and is never changed. This patch allows drivers to
declare there ethtool_ops structure read-only.Signed-off-by: Stephen Hemminger
Signed-off-by: Jeff Garzik
18 Jul, 2006
1 commit
-
Noticed by Willy Tarreau.
Signed-off-by: Jeff Garzik
23 Jun, 2006
1 commit
-
This patch adds a generic segmentation offload toggle that can be turned
on/off for each net device. For now it only supports in TCPv4.Signed-off-by: Herbert Xu
Signed-off-by: David S. Miller
18 Jun, 2006
2 commits
-
The function ethtool_get_ufo was referring to ETHTOOL_GTSO instead of
ETHTOOL_GUFO.Signed-off-by: Herbert Xu
Signed-off-by: David S. Miller -
The current stack treats NETIF_F_HW_CSUM and NETIF_F_NO_CSUM
identically so we test for them in quite a few places. For the sake
of brevity, I'm adding the macro NETIF_F_GEN_CSUM for these two. We
also test the disjunct of NETIF_F_IP_CSUM and the other two in various
places, for that purpose I've added NETIF_F_ALL_CSUM.Signed-off-by: Herbert Xu
Signed-off-by: David S. Miller
12 Jan, 2006
1 commit
-
net: Use where capable() is used.
Signed-off-by: Randy Dunlap
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
29 Oct, 2005
1 commit
-
Attached is kernel patch for UDP Fragmentation Offload (UFO) feature.
1. This patch incorporate the review comments by Jeff Garzik.
2. Renamed USO as UFO (UDP Fragmentation Offload)
3. udp sendfile support with UFOThis patches uses scatter-gather feature of skb to generate large UDP
datagram. Below is a "how-to" on changes required in network device
driver to use the UFO interface.UDP Fragmentation Offload (UFO) Interface:
-------------------------------------------
UFO is a feature wherein the Linux kernel network stack will offload the
IP fragmentation functionality of large UDP datagram to hardware. This
will reduce the overhead of stack in fragmenting the large UDP datagram to
MTU sized packets1) Drivers indicate their capability of UFO using
dev->features |= NETIF_F_UFO | NETIF_F_HW_CSUM | NETIF_F_SGNETIF_F_HW_CSUM is required for UFO over ipv6.
2) UFO packet will be submitted for transmission using driver xmit routine.
UFO packet will have a non-zero value for"skb_shinfo(skb)->ufo_size"
skb_shinfo(skb)->ufo_size will indicate the length of data part in each IP
fragment going out of the adapter after IP fragmentation by hardware.skb->data will contain MAC/IP/UDP header and skb_shinfo(skb)->frags[]
contains the data payload. The skb->ip_summed will be set to CHECKSUM_HW
indicating that hardware has to do checksum calculation. Hardware should
compute the UDP checksum of complete datagram and also ip header checksum of
each fragmented IP packet.For IPV6 the UFO provides the fragment identification-id in
skb_shinfo(skb)->ip6_frag_id. The adapter should use this ID for generating
IPv6 fragments.Signed-off-by: Ananda Raju
Signed-off-by: Rusty Russell (forwarded)
Signed-off-by: Arnaldo Carvalho de Melo
06 Sep, 2005
1 commit
-
Signed-off-by: Al Viro
Signed-off-by: Jeff Garzik
30 Aug, 2005
1 commit
-
This patch adds a new field to net device to hold the permanent
hardware address, and adds a new generic ethtool_op function to
get that address.Signed-off-by: Jon Wetzel
Signed-off-by: John W. Linville
Signed-off-by: David S. Miller
07 Jun, 2005
1 commit
-
It was checking the "GET" function pointer instead of
the "SET" one. Looks like a cut&paste error :-)Signed-off-by: David S. Miller
30 May, 2005
3 commits
-
Signed-off-by: Jon Mason
Signed-off-by: David S. Miller -
The features field in netdevice is really a bitmask, and bitmask's should
be unsigned.Signed-off-by: Stephen Hemminger
Signed-off-by: David S. Miller -
Resend of earlier patch (no changes) from Catalin used to provide
device feature change notification.Signed-off-by: Catalin BOIE
Acked-by: Stephen Hemminger
Signed-off-by: David S. Miller
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!
