- 24 Jul, 2009 7 commits
-
-
Ben Greear authored
This patch zero's the timestamp before handing the packet to the peer interface. This lets the peer recalculate the rx timestamp if it cares about timestamps. Signed-off-by:
Ben Greear <greearb@candelatech.com> Signed-off-by:
David S. Miller <davem@davemloft.net>
-
Sebastian Haas authored
This patch adds support to the ems_pci driver for the new, v2, 4 channel CPC-PCI/PCIe/104P CAN cards from EMS Dr. Thomas Wuensche. Signed-off-by:
Sebastian Haas <haas@ems-wuensche.com> Signed-off-by:
Wolfgang Grandegger <wg@grandegger.com> Signed-off-by:
-
Mike Rapoport authored
Signed-off-by:
Mike Rapoport <mike@compulab.co.il> Acked-by:
Ben Dooks <ben-linux@fluff.org> Signed-off-by:
-
Ajit Khaparde authored
This patch removes support for INET_LRO and switches over to GRO. Signed-off-by:
Ajit Khaparde <ajitk@serverengines.com> Signed-off-by:
-
Rémi Denis-Courmont authored
The per-socket drop count is visible via /proc/net/phonet. Signed-off-by:
Rémi Denis-Courmont <remi.denis-courmont@nokia.com> Signed-off-by:
-
Rémi Denis-Courmont authored
Signed-off-by:
-
Rémi Denis-Courmont authored
This provides a list of sockets with their Phonet bind addresses and some socket debug informations through /proc/net/phonet. Signed-off-by:
-
- 21 Jul, 2009 11 commits
-
-
Eilon Greenstein authored
Signed-off-by:
Eilon Greenstein <eilong@broadcom.com> Signed-off-by:
-
Eilon Greenstein authored
Signed-off-by:
-
Eilon Greenstein authored
Signed-off-by:
-
Eilon Greenstein authored
Adding support for BCM8727 - a dual port SFP+ PHY. That includes verification of the optic module vendor and part number - the list of approved modules resides on the nvram and the module is verified by the FW. Since not all users would like to use this verification feature, it can be disabled. The default behavior is to issue a warning if the module is not approved, but still allow using it - but it is also possible to disable the link if the module is not approved. Signed-off-by:
Yaniv Rosner <yanivr@broadcom.com> Signed-off-by:
-
Eilon Greenstein authored
As noted by Or Gerlitz <ogerlitz@Voltaire.com>, the vlan_features was not updated Signed-off-by:
-
Eilon Greenstein authored
Signed-off-by:
Vlad Zolotarov <vladz@broadcom.com> Signed-off-by:
-
Eilon Greenstein authored
Signed-off-by:
-
Eilon Greenstein authored
Check if fan failure happened before the driver was loaded and notify the user Signed-off-by:
-
Eilon Greenstein authored
Setup fan failure for different PHY types or according to nvram settings Signed-off-by:
-
Eilon Greenstein authored
Since management traffic cannot go on the wire while configured to loopback, simply stop it to avoid race condition when the MAC is set to loopback in the middle of a packet Signed-off-by:
-
Gerrit Renker authored
The local variable 'idev' shadows the function argument 'idev' to ip6_mc_add_src(). Fixed by removing the local declaration, as pmc->idev should be identical with 'idev' passed as argument. Signed-off-by:
Gerrit Renker <gerrit@erg.abdn.ac.uk> Acked-by:
David L Stevens <dlstevens@us.ibm.com> Signed-off-by:
-
- 20 Jul, 2009 21 commits
-
-
Andy Grover authored
Add a comment for what's going on. Remove negative logic. I find this much easier to understand quickly, although there are a few lines duplicated. Signed-off-by:
Andy Grover <andy.grover@oracle.com> Signed-off-by:
-
Andy Grover authored
In iWARP code, node_type will always be RNIC Signed-off-by:
-
Andy Grover authored
The existing code treated page_shift as a variable, when in fact we always want to have the fastreg page size be the same as the arch's page size -- and it is, so this doesn't need to be a variable. Signed-off-by:
-
Andy Grover authored
While FMRs allow significant flexibility in what size of pages they can use, we really just want FMR pages to match CPU page size. Roland says we can count on this always being supported, so this simplifies things. Signed-off-by:
-
Andy Grover authored
Completion or congestion notifications were not being checked if the socket went to sleep. This patch fixes that. Signed-off-by:
-
Andy Grover authored
Signed-off-by:
-
Andy Grover authored
Backwards compatibility with rds 3.0 causes protocol- based flow control to be disabled as a side-effect. I don't want to pull out FC support from the IB transport but I do want to document and keep the sysctl consistent if possible. Signed-off-by:
-
Andy Grover authored
Since RDS 3.0 and 3.1 have different packet formats, we need to wait until after protocol negotiation is complete to layout the rx buffers. Signed-off-by:
-
Andy Grover authored
Protocol negotiation is logically a property of the transports, so rds core need not set it. Signed-off-by:
-
Andy Grover authored
Of course len is in bytes. Calling it data_len hopefully indicates a little better what the variable is actually for. Signed-off-by:
-
Andy Grover authored
Signed-off-by:
-
Andy Grover authored
Signed-off-by:
-
Andy Grover authored
The big differences between RDS 3.0 and 3.1 are protocol-level flow control, and with 3.1 the header is in front of the data. The header always ends up in the header buffer, and the data goes in the data page. In 3.0 our "header" is a trailer, and will end up either in the data page, the header buffer, or split across the two. Since 3.1 is backwards- compatible with 3.0, we need to continue to support these cases. This patch does that -- if using RDS 3.0 wire protocol, it will copy the header from wherever it ended up into the header buffer. Signed-off-by:
-
Andy Grover authored
RDS on IB uses privdata to do protocol version negotiation. Apparently the IB stack will return a larger privdata buffer than the struct we were expecting. Just to be extra-sure, this patch adds some checks in this area. Signed-off-by:
-
Andy Grover authored
This will be default cause IB connections to failover faster, but allow a longer retry count to be used if desired. Signed-off-by:
-
Johannes Berg authored
Eric explained this to me -- and afterwards the comment made sense, but not before. Add the the critical point about interfaces having to be gone from the netns before subsys notifiers are called. Signed-off-by:
Johannes Berg <johannes@sipsolutions.net> Signed-off-by:
-
roel kluin authored
strlcpy() will always null terminate the string. Also use the sizeof(version) to strlcopy() the version string. Signed-off-by:
Roel Kluin <roel.kluin@gmail.com> Signed-off-by:
-
Jarek Poplawski authored
While looking for other fib_trie problems reported by Pawel Staszewski I noticed there are a few uses of tnode_get_child() and node_parent() in lookups instead of their rcu versions. Signed-off-by:
Jarek Poplawski <jarkao2@gmail.com> Signed-off-by:
-
Jarek Poplawski authored
During large updates there could be triggered warnings like: "Fix inflate_threshold_root. Now=25 size=11 bits" if inflate() of the root node isn't finished in 10 loops. It should be much rarer now, after changing the threshold from 15 to 25, and a temporary problem, so this patch tries to handle it automatically using a fix variable to increase by one inflate threshold for next root resizes (up to the 35 limit, max fix = 10). The fix variable is decreased when root's inflate() finishes below 7 loops (even if some other, smaller table/ trie is updated -- for simplicity the fix variable is global for now). Reported-by:
Pawel Staszewski <pstaszewski@itcare.pl> Reported-by:
Jorge Boncompte [DTI2] <jorge@dti2.net> Tested-by:
Robert Olsson <robert.olsson@its.uu.se> Signed-off-by:
-
Jarek Poplawski authored
During trie_rebalance() we free memory after resizing with call_rcu(), but large updates, especially with PREEMPT_NONE configs, can cause memory stresses, so this patch calls synchronize_rcu() in tnode_free_flush() after each sync_pages to guarantee such freeing (especially before resizing the root node). The value of sync_pages = 128 is based on Pawel Staszewski's tests as the lowest which doesn't hinder updating times. (For testing purposes there was a sysfs module parameter to change it on demand, but it's removed until we're sure it could be really useful.) The patch is based on suggestions by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Reported-by:
-
Herbert Xu authored
When the physical MTU changes we want to ensure that all existing VLAN device MTUs do not exceed the new underlying MTU. This patch adds that propagation. Signed-off-by:
Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by:
-
- 17 Jul, 2009 1 commit
-
-
Mike Frysinger authored
The connector test code currently does not work out of the box. This is because it uses a connector id that is above the registered limit. So rather than force people to stumble through undocumented code wondering why it isn't working, have the test code use one of the "private" ids by default. While I'm in here, clean up the code (kernel and user app) so that it's a bit more user friendly and verbose in significant things that it does. Terse test code wastes people time as they simply enumerate it with all the same kind of debug messages to get a better feel of what code is running at any time. Signed-off-by:
Mike Frysinger <vapier@gentoo.org> Signed-off-by:
-
