- 30 Oct, 2009 6 commits
-
-
Stephen Hemminger authored
This is a new ID that just showed up in latest vendor driver. Signed-off-by:
Stephen Hemminger <shemminger@vyatta.com> Signed-off-by:
David S. Miller <davem@davemloft.net>
-
Ben Hutchings authored
Now that we can tell whether GRO is being applied, this heuristic is effective once more. Signed-off-by:
Ben Hutchings <bhutchings@solarflare.com> Signed-off-by:
-
Ben Hutchings authored
When GRO is successfully merging received packets, we should allocate raw page buffers rather than skbs that will be discarded by GRO. Otherwise, we should allocate skbs. GRO also benefits from higher interrupt moderation, so increase the score for mergeable RX packets. Signed-off-by:
-
Ben Hutchings authored
This will allow drivers to adjust their receive path dynamically based on whether GRO is being applied successfully. Currently all in-tree callers ignore the return values of these functions and do not need to be changed. Signed-off-by:
Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by:
-
Ben Hutchings authored
This clarifies which return and parameter types are GRO result codes and not RX result codes. Signed-off-by:
-
David S. Miller authored
-
- 29 Oct, 2009 34 commits
-
-
Gabor Gombas authored
Currently PACKET_TX_RING forces certain amount of every frame to remain unused. This probably originates from an early version of the PACKET_TX_RING patch that in fact used the extra space when the (since removed) CONFIG_PACKET_MMAP_ZERO_COPY option was enabled. The current code does not make any use of this extra space. This patch removes the extra space reservation and lets userspace make use of the full frame size. Signed-off-by:
Gabor Gombas <gombasg@sztaki.hu> Signed-off-by:
-
Cyrill Gorcunov authored
proto_ops->getname implies copying protocol specific data into storage unit (particulary to __kernel_sockaddr_storage). So when we implement new protocol support we should keep such a detail in mind (which is easy to forget about). Lets introduce DECLARE_SOCKADDR helper which check if storage unit is not overfowed at build time. Eventually inet_getname is switched to use DECLARE_SOCKADDR (to show example of usage). Signed-off-by:
Cyrill Gorcunov <gorcunov@openvz.org> Signed-off-by:
-
-
Eric Dumazet authored
Some workloads hit dev_base_lock rwlock pretty hard. We can use RCU lookups to avoid touching this rwlock. netdevices are already freed after a RCU grace period, so this patch adds no penalty at device dismantle time. dev_ifname() converted to dev_get_by_index_rcu() Signed-off-by:
Eric Dumazet <eric.dumazet@gmail.com> Signed-off-by:
-
roel kluin authored
The variables are unsigned so the `< 0' test always fails, the other part of the test catches wrapped values. Signed-off-by:
Roel Kluin <roel.kluin@gmail.com> Signed-off-by:
-
roel kluin authored
optlen is unsigned so the `< 0' test is never true. Signed-off-by:
-
roel kluin authored
If there is data, the unsigned skb->len is greater than 0. rt.sigdigits is unsigned as well, so the test `>= 0' is always true, the other part of the test catches wrapped values. Signed-off-by:
-
Tilman Schmidt authored
Replace the sequence of strcmp calls for interpreting ZSAU parameter strings by a table of known strings and lookup loop to improve readability. Impact: readability improvement, no functional change Signed-off-by:
Tilman Schmidt <tilman@imap.cc> Signed-off-by:
-
Tilman Schmidt authored
On more step towards the holy grail of checkpatch.pl silence. Impact: cosmetic Signed-off-by:
-
Tilman Schmidt authored
On the quest for the holy grail of checkpatch.pl silence. Impact: cosmetic Signed-off-by:
-
Tilman Schmidt authored
Duly uglified as demanded by checkpatch.pl. Impact: cosmetic Signed-off-by:
-
Tilman Schmidt authored
Dum sanctis checkpatch.pl'ae legibus obsequimur. Impact: cosmetic Signed-off-by:
-
Tilman Schmidt authored
Reorganize the code of the Gigaset M10x driver to make it more readable, less redundant, better aligned to the style of other parts of the driver, and cause fewer checkpatch.pl complaints. Impact: code reorganization, no functional change Signed-off-by:
-
Tilman Schmidt authored
The CAPI interface incorrectly assumed that CAPI messages would always start at the beginning of the data buffer: fix by treating DATA_B3 messages as the link layer header to their payload data. This fix changes the way acknowledgement information is propagated through the hardware specific modules and thereby impacts the ISDN4Linux variant of the driver, too. Also some assumptions about methods not being called from interrupt context turned out to be unwarranted; fix by using dev_kfree_skb_any() wherever non-interrupt context isn't guaranteed. Impact: bugfix Signed-off-by:
-
Tilman Schmidt authored
A missing dot lead to garbage characters being included in the dial command generated from a CAPI CONNECT_REQ message, which interestingly enough worked anyway, illustrating the resilience of the device. Impact: bugfix Signed-off-by:
-
Tilman Schmidt authored
Replace the "ignoring Additional Info" warning message by better readable ones citing the specific subparameters being ignored. Make parts of the code more readable by using a local cmsg pointer variable. Impact: readability improvement Signed-off-by:
-
Gilad Ben-Yossef authored
Add and use no DSCAK bit in the features field. Signed-off-by:
Gilad Ben-Yossef <gilad@codefidence.com> Sigend-off-by:
Ori Finkelman <ori@comsleep.com> Sigend-off-by:
Yony Amit <yony@comsleep.com> Signed-off-by:
-
Gilad Ben-Yossef authored
Add and use no window scale bit in the features field. Note that this is not the same as setting a window scale of 0 as would happen with window limit on route. Signed-off-by:
-
Gilad Ben-Yossef authored
Implement querying and acting upon the no timestamp bit in the feature field. Signed-off-by:
-
Gilad Ben-Yossef authored
Implement querying and acting upon the no sack bit in the features field. Signed-off-by:
-
Gilad Ben-Yossef authored
Adding an accessor to existing dst_entry feautres field and refactor the only supported feature (allfrag) to use it. Signed-off-by:
-
Gilad Ben-Yossef authored
We need tcp_parse_options to be aware of dst_entry to take into account per dst_entry TCP options settings Signed-off-by:
-
Gilad Ben-Yossef authored
Since we only use tcp_parse_options here to check for the exietence of TCP timestamp option in the header, it is better to call with the "established" flag on. Signed-off-by:
-
Janusz Krzysztofik authored
I found that the current version of drivers/net/usb/dm9601.c can be used to successfully drive a low-power, low-cost network adapter with USB ID 0a46:9000, based on a DM9000E chipset. As no device with this ID is yet present in the kernel, I have created a patch that adds support for the device to the dm9601 driver. Created and tested against linux-2.6.32-rc5. Signed-off-by:
Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> Acked-by:
Peter Korsgaard <jacmet@sunsite.dk> Signed-off-by:
-
Ron Mercer authored
The mailbox command process would only process a maximum of 5 unrelated firmware events while waiting for it's command completion status. It should process an unlimited number of events while waiting for a maximum of 5 seconds. Signed-off-by:
Ron Mercer <ron.mercer@qlogic.com> Signed-off-by:
-
Ron Mercer authored
Clean up driver resources without touch the hardware. Add pci save/restore state. Signed-off-by:
-
Eric Dumazet authored
Speedup module unloading by factorizing synchronize_rcu() calls Signed-off-by:
-
Eric Dumazet authored
Speedup module unloading by factorizing synchronize_rcu() calls Signed-off-by:
-
Eric Dumazet authored
Speedup module unloading by factorizing synchronize_rcu() calls Signed-off-by:
-
Eric Dumazet authored
Speedup module unloading by factorizing synchronize_rcu() calls Signed-off-by:
-
Eric Dumazet authored
Speedup module unloading by factorizing synchronize_rcu() calls Signed-off-by:
-
Ajit Khaparde authored
This patch adds the PCI IDs for the next generation chip to the PCI_DEVICE_ID table. Signed-off-by:
Ajit Khaparde <ajitk@serverengines.com> Signed-off-by:
-
Neil Horman authored
Augment raw_send_hdrinc to correct for incorrect ip header length values A series of oopses was reported to me recently. Apparently when using AF_RAW sockets to send data to peers that were reachable via ipsec encapsulation, people could panic or BUG halt their systems. I've tracked the problem down to user space sending an invalid ip header over an AF_RAW socket with IP_HDRINCL set to 1. Basically what happens is that userspace sends down an ip frame that includes only the header (no data), but sets the ip header ihl value to a large number, one that is larger than the total amount of data passed to the sendmsg call. In raw_send_hdrincl, we allocate an skb based on the size of the data in the msghdr that was passed in, but assume the data is all valid. Later during ipsec encapsulation, xfrm4_tranport_output moves the entire frame back in the skbuff to provide headroom for the ipsec headers. During this operation, the skb->transport_header is repointed to a spot computed by skb->network_header + the ip header length (ihl). Since so little data was passed in relative to the value of ihl provided by the raw socket, we point transport header to an unknown location, resulting in various crashes. This fix for this is pretty straightforward, simply validate the value of of iph->ihl when sending over a raw socket. If (iph->ihl*4U) > user data buffer size, drop the frame and return -EINVAL. I just confirmed this fixes the reported crashes. Signed-off-by:
Neil Horman <nhorman@tuxdriver.com> Acked-by:
-
-
