- 03 Aug, 2010 2 commits
-
-
Changli Gao authored
6c79bf0f subtracts PPPOE_SES_HLEN from mtu at the front of ip_fragment(). So the later subtraction should be removed. The MTU of 802.1q is also 1500, so MTU should not be changed. Signed-off-by:
Changli Gao <xiaosuo@gmail.com> Signed-off-by:
Bart De Schuymer <bdschuym@pandora.bo> ---- net/ipv4/ip_output.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) Signed-off-by:
David S. Miller <davem@davemloft.net>
-
Josh Hunt authored
Initial TCP thin-stream commit did not add getsockopt support for the new socket options: TCP_THIN_LINEAR_TIMEOUTS and TCP_THIN_DUPACK. This adds support for them. Signed-off-by:
Josh Hunt <johunt@akamai.com> Tested-by:
Andreas Petlund <apetlund@simula.no> Acked-by:
-
- 02 Aug, 2010 36 commits
-
-
Dimitris Michailidis authored
Signed-off-by:
Dimitris Michailidis <dm@chelsio.com> Signed-off-by:
-
Dimitris Michailidis authored
Signed-off-by:
-
Dimitris Michailidis authored
Signed-off-by:
-
Dimitris Michailidis authored
Add support for running the driver on any PCI function. Mostly this entails replacing a constant 0 in a number of calls with the variable function number. Signed-off-by:
-
Dimitris Michailidis authored
The device supports TSO+ECN. Signed-off-by:
-
Dimitris Michailidis authored
Get info about the availability of Tx on-chip queues from FW and if they are supported set up a memory window for them. iw_cxgb4 will be using them. Move the existing window setup later in the init sequence, after we have collected the new info. Signed-off-by:
-
Dimitris Michailidis authored
Commit 1704d748 ("cxgb4vf: small changes to message processing structures/macros") was incomplete and causes cxgb4 to write bad TSO descriptors. Fix that up by reverting the offending part of that commit and adjusting field accesses now that they are one level deeper. Signed-off-by:
-
Dimitris Michailidis authored
The checksum provided by the device doesn't include the L3 headers, as IPv6 expects. Signed-off-by:
-
Dimitris Michailidis authored
Signed-off-by:
-
Dan Carpenter authored
There was an error path where "mem_ptr_virt" didn't get unmapped. Signed-off-by:
Dan Carpenter <error27@gmail.com> Signed-off-by:
-
Krzysztof Hałasa authored
SBE 2T3E3 cards use DECchips 21143 but they need a different driver. Don't even try to use a normal tulip driver with them. Signed-off-by:
Krzysztof Hałasa <khc@pm.waw.pl> Signed-off-by:
-
Joe Perches authored
Remove locally defined equivalents Signed-off-by:
Joe Perches <joe@perches.com> Signed-off-by:
-
-
Matt Carlson authored
This patch updates the tg3 version to 3.113. Reviewed-by:
Benjamin Li <benli@broadcom.com> Reviewed-by:
Michael Chan <mchan@broadcom.com> Signed-off-by:
Matt Carlson <mcarlson@broadcom.com> Signed-off-by:
-
Matt Carlson authored
This patch moves most of the phy related flag definitions over to the phyflags member and changes the code accordingly. Reviewed-by:
-
Matt Carlson authored
This patch deletes the link_config.phy_is_low_power flag and creates a new phy_flags device member to store all phy related settings. All the code is converted accordingly. Reviewed-by:
-
Matt Carlson authored
This patch replaces some instances of hardcoded phy register values with preprocessor equivalents. Reviewed-by:
-
Matt Carlson authored
This patch adds error reporting to the tg3_phydsp_write() function and converts a few more locations to use this function over the inlined equivalent. Reviewed-by:
-
Matt Carlson authored
smp_mb() inside tg3_tx_avail() is used twice in the normal tg3_start_xmit() path (see illustration below). The full memory barrier is only necessary during race conditions with tx completion. We can speed up the tx path by replacing smp_mb() in tg3_tx_avail() with a compiler barrier. The compiler barrier is to force the compiler to fetch the tx_prod and tx_cons from memory. In the race condition between tg3_start_xmit() and tg3_tx(), we have the following situation: tg3_start_xmit() tg3_tx() if (!tg3_tx_avail()) BUG(); ... if (!tg3_tx_avail()) netif_tx_stop_queue(); update_tx_index(); smp_mb(); smp_mb(); if (tg3_tx_avail()) if (netif_tx_queue_stopped() && netif_tx_wake_queue(); tg3_tx_avail()) With smp_mb() removed from tg3_tx_avail(), we need to add smp_mb() to tg3_start_xmit() as shown above to properly order netif_tx_stop_queue() and tg3_tx_avail() to check the ring index. If it is not strictly ordered, the tx queue can be stopped forever. This improves performance by about 3% with 2 ports running bi-directional 64-byte packets. Reviewed-by: -
Matt Carlson authored
These devices were never released to the public. Reviewed-by:
-
Matt Carlson authored
This patch adds code to determine the APE firmware type and report this along with the firmware version. Reviewed-by:
-
Matt Carlson authored
The ASPM workaround setting obtained from NVRAM only works with devices older than 5717. This patch enforces the restriction. Reviewed-by:
-
Matt Carlson authored
This patch changes the code to only manage the PCIe gphy power for CPMU-less devices only. The CPMU takes over management for newer chips. Reviewed-by:
-
Matt Carlson authored
The phy test register location has been repurposed for 5717+ devices. This patch changes the code to avoid this location for these devices. Reviewed-by:
-
Matt Carlson authored
This patch creates a TG3_FLG3_5717_PLUS flag to collectively describe the set of changes in the ASIC that will apply to all future chip revisions. Signed-off-by:
-
Matt Carlson authored
The TSS flag needs to be turned off during tg3_close(). If the device fails to allocate more than one MSI-X vector the next time the device is brought up, transmits will fail. Signed-off-by:
-
Matt Carlson authored
tg3 commit e7126997 entitled "tg3: Preserve PCIe MPS setting for new devs" attempted to ensure the PCIe link negotiated Maximum Payload Size (MPS) setting was 128 bytes for all devices that didn't support higher speeds. The 5784 device was mistakenly added to this list when it shouldn't have. This patch removes the 5784 ASIC rev devices from that list. Reviewed-by:
-
-
Changli Gao authored
use skb->len for accounting as xt_quota does. Since nf_conntrack works at the network layer, skb_network_offset should always returns ZERO. Signed-off-by:
Patrick McHardy <kaber@trash.net>
-
Changli Gao authored
The tuple got from unique_tuple() doesn't need to be really unique, so the check for the unique tuple isn't necessary, when there isn't any other choice. Eliminating the unnecessary nf_nat_used_tuple() can save some CPU cycles too. Signed-off-by:
-
Changli Gao authored
The only user of unique_tuple() get_unique_tuple() doesn't care about the return value of unique_tuple(), so make unique_tuple() return void (nothing). Signed-off-by:
-
Changli Gao authored
Use local variable hdrlen instead of ip_hdrlen(skb). Signed-off-by:
-
Simon Horman authored
This removes duplicate code by providing a default implementation which is used by 3 of the 4 modules that provide these call. Signed-off-by:
Simon Horman <horms@verge.net.au> Signed-off-by:
-
Simon Horman authored
IPVS was merged into the kernel quite a long time ago and has been seeing wide-spread production use for even longer. It seems appropriate for it to be no longer tagged as EXPERIMENTAL Signed-off-as: Simon Horman <horms@verge.net.au> Signed-off-by: -
Changli Gao authored
some users of nf_ct_ext_exist() know ct->ext isn't NULL. For these users, the check for ct->ext isn't necessary, the function __nf_ct_ext_exist() can be used instead. the type of the return value of nf_ct_ext_exist() is changed to bool. Signed-off-by:
-
Eric Dumazet authored
We currently disable BH for the whole duration of get_counters() On machines with a lot of cpus and large tables, this might be too long. We can disable preemption during the whole function, and disable BH only while fetching counters for the current cpu. Signed-off-by:
Eric Dumazet <eric.dumazet@gmail.com> Signed-off-by:
-
- 01 Aug, 2010 2 commits
-
-
Stephen Hemminger authored
If user misconfigures ingress and causes a redirection loop, don't overwhelm the log. This is also a error case so make it unlikely. Found by inspection, luckily not in real system. Signed-off-by:
Stephen Hemminger <shemminger@vyatta.com> Signed-off-by:
-
Julia Lawall authored
The other calls to kmalloc in the same function use GFP_ATOMIC, and indeed two locks are held within the body of the function. The semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/) // <smpl> @@ identifier f; @@ *f(...,GFP_ATOMIC,...) ... when != spin_unlock(...) when != read_unlock(...) when != write_unlock(...) when != read_unlock_irq(...) when != write_unlock_irq(...) when != read_unlock_irqrestore(...) when != write_unlock_irqrestore(...) when != spin_unlock_irq(...) when != spin_unlock_irqrestore(...) *f(...,GFP_KERNEL,...) // </smpl> Signed-off-by:
Julia Lawall <julia@diku.dk> Signed-off-by:
-
