- 21 Oct, 2010 40 commits
-
-
Guo-Fu Tseng authored
Adding read memory barrier in between flag reading and data reading of receive descriptors. This prevents the data being read before hardware complete writing informations. Reported-by:
Stefan Hajnoczi <stefanha@gmail.com> Signed-off-by:
Guo-Fu Tseng <cooldavid@cooldavid.org> Signed-off-by:
David S. Miller <davem@davemloft.net>
-
Guo-Fu Tseng authored
Explains what `fdc` variable is for. Signed-off-by:
-
Guo-Fu Tseng authored
Adding phy_on in opposition to phy_off. Signed-off-by:
-
Bandan Das authored
checkpatch.pl cleanup : Remove braces from single statement blocks. Signed-off-by:
Bandan Das <bandan.das@stratus.com> Signed-off-by:
-
Bandan Das authored
checkpatch.pl cleanup: Added spaces around operators at various places. Also fixed some c99 style comments that I came across. Signed-off-by:
-
Tracey Dent authored
Changed <module>-objs to <module>-y in Makefile. Signed-off-by:
Tracey Dent <tdent48227@gmail.com> Signed-off-by:
-
Bernard Blackham authored
The smsc95xx driver currently generates a new random MAC address every time the interface is brought up. This makes it impossible to override using the standard `ifconfig hw ether` approach. Past patches tried to make the MAC address a module parameter or base it off the die ID, but it seems to me much simpler (and hopefully less controversial) to stick with the current random generation scheme, but allow the user to change the address. This patch does exactly that - it moves the random address generation from smsc95xx_reset() into smsc95xx_bind(), so that it is done once on module load, not on every ifup. The user can then override this using the standard mechanisms. Applies against 2.6.35 and linux-2.6 head. Signed-off-by:
Bernard Blackham <b-omap@largestprime.net> Signed-off-by:
-
Michael Chan authored
A number of customers are reporting packet loss under certain workloads (e.g. heavy bursts of small packets) with flow control disabled. A larger rx ring helps to prevent these losses. No change in default rx ring size and memory consumption. Signed-off-by:
Andy Gospodarek <andy@greyhouse.net> Acked-by:
John Feeney <jfeeney@redhat.com> Signed-off-by:
Michael Chan <mchan@broadcom.com> Signed-off-by:
-
Changli Gao authored
The first parameter dev isn't in use in qdisc_create_dflt(). Signed-off-by:
Changli Gao <xiaosuo@gmail.com> Acked-by:
Jamal Hadi Salim <hadi@cyberus.ca> Signed-off-by:
-
stephen hemminger authored
Only used in main file. Signed-off-by:
Stephen Hemminger <shemminger@vyatta.com> Acked-by:
Jay Vosburgh <fubar@us.ibm.com> Signed-off-by:
-
stephen hemminger authored
Only used in one place. Signed-off-by:
-
stephen hemminger authored
The function rtnl_kill_links is defined but never used. Signed-off-by:
-
stephen hemminger authored
Function only defined and used in one file. Signed-off-by:
-
stephen hemminger authored
Make routines that are only used in one file static. Signed-off-by:
-
stephen hemminger authored
Gcc doesn't usually handle inline across compilation units, and the functions don't have to be global in scope. Move the set/reset flag functions int the existing vmxnet3 header. Signed-off-by:
Shreyas Bhatewara <sbhatewara@vmware.com> Signed-off-by:
-
stephen hemminger authored
Signed-off-by:
Flavio Leitner <fleitner@redhat.com> Signed-off-by:
-
stephen hemminger authored
Make local functions and variable static. Do some rearrangement of the string table stuff to put it where it gets used. Signed-off-by:
Ben Hutchings <bhutchings@solarflare.com> Signed-off-by:
-
stephen hemminger authored
Signed-off-by:
-
stephen hemminger authored
A couple of functions in socket.c are only used there and should be localized. Signed-off-by:
-
stephen hemminger authored
Signed-off-by:
-
Eric Dumazet authored
Perf tools session at NFWS 2010 pointed out a false sharing on struct fib_alias that can be avoided pretty easily, if we set FA_S_ACCESSED bit only if needed (ie : not already set) Signed-off-by:
Eric Dumazet <eric.dumazet@gmail.com> Signed-off-by:
-
Eric Dumazet authored
Under network load, doing : tc qdisc del dev eth0 root triggers : [ 167.193087] BUG: spinlock bad magic on CPU#3, udpflood/4928 [ 167.193139] lock: c15bc324, .magic: 00000000, .owner: <none>/-1, .owner_cpu: -1 [ 167.193193] Pid: 4928, comm: udpflood Not tainted 2.6.36-rc7-11417-g215340c-dirty #323 [ 167.193245] Call Trace: [ 167.193292] [<c13abaa0>] ? printk+0x18/0x20 [ 167.193342] [<c11afb53>] spin_bug+0xa3/0xf0 [ 167.193389] [<c11afcdd>] do_raw_spin_lock+0x7d/0x160 [ 167.193440] [<c1313d4e>] ? __dev_xmit_skb+0x27e/0x2b0 [ 167.193496] [<c107382b>] ? trace_hardirqs_on+0xb/0x10 [ 167.193545] [<c13ae99a>] _raw_spin_lock+0x3a/0x40 [ 167.193593] [<c1313d4e>] ? __dev_xmit_skb+0x27e/0x2b0 [ 167.193641] [<c1313d4e>] __dev_xmit_skb+0x27e/0x2b0 commit 79640a4c (add additional lock to qdisc to increase throughput) forgot to initialize noop_qdisc and noqueue_qdisc busylock Signed-off-by:
-
Stanislaw Gruszka authored
If dma mapping fail we are dropping packages or fail to open device. But exact reason of drop/fail stays unknow for a user, so print errors. Signed-off-by:
Stanislaw Gruszka <sgruszka@redhat.com> Signed-off-by:
-
Stanislaw Gruszka authored
Fix switching device to low-speed mode after resume reported in: https://bugzilla.redhat.com/show_bug.cgi?id=502974Reported-and-tested-by:
Laurentiu Badea <bugzilla-redhat@wotevah.com> Signed-off-by:
-
Stanislaw Gruszka authored
Since we do not change rx buffer size any longer, we can clean up rtl8169_change_mtu and in consequence rtl8169_down. Signed-off-by:
-
Stanislaw Gruszka authored
Only increase tx_{packets,dropped} statistics when transmit or drop full skb, not just fragment. Signed-off-by: -
Stanislaw Gruszka authored
Signed-off-by:
-
Stanislaw Gruszka authored
Signed-off-by:
-
Stanislaw Gruszka authored
Signed-off-by:
-
Stanislaw Gruszka authored
Check possible dma mapping errors and do clean up if it happens. Fix overwrap bug in rtl8169_tx_clear on the way. Signed-off-by:
-
Hao Zheng authored
Make the bnx2x driver use the new vlan accleration model. Signed-off-by:
Hao Zheng <hzheng@nicira.com> Signed-off-by:
Jesse Gross <jesse@nicira.com> CC: Eilon Greenstein <eilong@broadcom.com> Signed-off-by:
-
Jesse Gross authored
Make the ixgbe driver use the new vlan accleration model. Signed-off-by:
-
Jesse Gross authored
Make the bnx2 driver use the new vlan accleration model. Signed-off-by:
-
Jesse Gross authored
If some of the underlying devices support it, enable vlan offload on transmit for bridge devices. This allows senders to take advantage of the hardware support, similar to other forms of acceleration. Signed-off-by:
-
Jesse Gross authored
Now that vlan acceleration is handled consistently regardless of usage, it is possible to enable and disable it at will. This adds support for Ethtool operations that change the offloading status for debugging purposes, similar to other forms of hardware acceleration. Signed-off-by:
-
Jesse Gross authored
Currently each driver that is capable of vlan hardware acceleration must be aware of the vlan groups that are configured and then pass the stripped tag to a specialized receive function. This is different from other types of hardware offload in that it places a significant amount of knowledge in the driver itself rather keeping it in the networking core. This makes vlan offloading function more similarly to other forms of offloading (such as checksum offloading or TSO) by doing the following: * On receive, stripped vlans are passed directly to the network core, without attempting to check for vlan groups or reconstructing the header if no group * vlans are made less special by folding the logic into the main receive routines * On transmit, the device layer will add the vlan header in software if the hardware doesn't support it, instead of spreading that logic out in upper layers, such as bonding. There are a number of advantages to this: * Fixes all bugs with drivers incorrectly dropping vlan headers at once. * Avoids having to disable VLAN acceleration when in promiscuous mode (good for bridging since it always puts devices in promiscuous mode). * Keeps VLAN tag separate until given to ultimate consumer, which avoids needing to do header reconstruction as in tg3 unless absolutely necessary. * Consolidates common code in core networking. Signed-off-by:
-
Jesse Gross authored
A struct net_device always maps to zero or one vlan groups and we always know the device when we are looking up a group. We currently do a hash table lookup on the device to find the group but it is much simpler to just store a pointer. Signed-off-by:
-
Jesse Gross authored
Currently users of hardware vlan accleration need to know whether the device supports it before generating packets. However, vlan acceleration will soon be available in a more flexible manner so knowing ahead of time becomes much more difficult. This adds a software fallback path for vlan packets on devices without the necessary offloading support, similar to other types of hardware accleration. Signed-off-by:
-
Jesse Gross authored
Many (but not all) drivers check to see whether there is a vlan group configured before using a tag stored in the skb. There's not much point in this check since it just throws away data that should only be present in the expected circumstances. However, it will soon be legal and expected to get a vlan tag when no vlan group is configured, so remove this check from all drivers to avoid dropping the tags. Signed-off-by:
-
Jesse Gross authored
VLAN_GROUP_ARRAY_LEN is simply the number of possible vlan VIDs. Since vlan groups will soon be more of an implementation detail for vlan devices, rename the constant to be descriptive of its actual purpose. Signed-off-by:
-
