- 30 Oct, 2014 29 commits
-
-
Eric Dumazet authored
bnx2x_msix_fp_int() and bnx2x_interrupt() run from hard interrupt context. They can use napi_schedule_irqoff() instead of napi_schedule() Signed-off-by:
Eric Dumazet <edumazet@google.com> Cc: Ariel Elior <ariel.elior@qlogic.com> Signed-off-by:
David S. Miller <davem@davemloft.net>
-
Eric Dumazet authored
mlx4_en_rx_irq() and mlx4_en_tx_irq() run from hard interrupt context. They can use napi_schedule_irqoff() instead of napi_schedule() Signed-off-by:
Amir Vadai <amirv@mellanox.com> Signed-off-by:
-
stephen hemminger authored
Signed-off-by:
Stephen Hemminger <stephen@networkplumber.org> Signed-off-by:
-
Haiyang Zhang authored
This will allow the workload spreading via vRSS for IPv6. Signed-off-by:
Haiyang Zhang <haiyangz@microsoft.com> Reviewed-by:
K. Y. Srinivasan <kys@microsoft.com> Signed-off-by:
-
Alexey Andriyanov authored
The fallback device is in ipv6 mode by default. The mode can not be changed in runtime, so there is no way to decapsulate ip4in6 packets coming from various sources without creating the specific tunnel ifaces for each peer. This allows to update the fallback tunnel device, but only the mode could be changed. Usual command should work for the fallback device: `ip -6 tun change ip6tnl0 mode any` The fallback device can not be hidden from the packet receiver as a regular tunnel, but there is no need for synchronization as long as we do single assignment. Cc: David S. Miller <davem@davemloft.net> Cc: Eric Dumazet <edumazet@google.com> Signed-off-by:
Alexey Andriyanov <alan@al-an.info> Signed-off-by:
-
Fabian Frederick authored
Do assignment before if condition and test !skb like in rawv6_recvmsg() Signed-off-by:
Fabian Frederick <fabf@skynet.be> Signed-off-by:
-
Fabian Frederick authored
remove __inline__ / inline and let compiler decide what to do with static functions Inspired-by:
-
Fabian Frederick authored
Signed-off-by:
-
Fabian Frederick authored
Apply commit e0f36310 ("ipx: remove unnecessary casting on ntohl") to all seq_printf/08lX Inspired-by:
Joe Perches <joe@perches.com> Signed-off-by:
-
David S. Miller authored
Alexei Starovoitov says: ==================== bpf: reduce verifier memory consumption and add tests Small set of cleanups: - reduce verifier memory consumption - add verifier test to check register state propagation and state equivalence - add JIT test reduced from recent nmap triggered crash ==================== Signed-off-by: -
Alexei Starovoitov authored
nmap generates classic BPF programs to filter ARP packets with given target MAC which triggered a bug in eBPF x64 JIT. The bug was fixed in commit e0ee9c12 ("x86: bpf_jit: fix two bugs in eBPF JIT compiler") This patch is adding a testcase in eBPF instructions (those that were generated by classic->eBPF converter) to be processed by JIT. The test is primarily targeting JIT compiler. Signed-off-by:
Alexei Starovoitov <ast@plumgrid.com> Signed-off-by:
-
Alexei Starovoitov authored
- add a test specifically targeting verifier state pruning. It checks state propagation between registers, storing that state into stack and state pruning algorithm recognizing equivalent stack and register states. - add summary line to spot failures easier Signed-off-by:
-
Alexei Starovoitov authored
verifier keeps track of register state spilled to stack. registers are 8-byte wide and always aligned, so instead of tracking them in every byte-sized stack slot, use MAX_BPF_STACK / 8 array to track spilled register state. Though verifier runs in user context and its state freed immediately after verification, it makes sense to reduce its memory usage. This optimization reduces sizeof(struct verifier_state) from 12464 to 1712 on 64-bit and from 6232 to 1112 on 32-bit. Note, this patch doesn't change existing limits, which are there to bound time and memory during verification: 4k total number of insns in a program, 1k number of jumps (states to visit) and 32k number of processed insn (since an insn may be visited multiple times). Theoretical worst case memory during verification is 1712 * 1k = 17Mbyte. Out-of-memory situation triggers cleanup and rejects the program. Suggested-by:
Andy Lutomirski <luto@amacapital.net> Signed-off-by:
-
David S. Miller authored
Guenter Roeck says: ==================== net: dsa: Fixes and enhancements Patch 01/15 addresses a bug indicated by an an annoying and unhelpful log message. Patches 02/15 and 03/15 are minor enhancements, adding support for known switch revisions. Patches 04/15 and 05/15 add support for MV88E6352 and MV88E6176. Patch 06/15 adds support for hardware monitoring, specifically for reporting the chip temperature, to the dsa subsystem. Patches 07/15 and 08/15 implement hardware monitoring for MV88E6352, MV88E6176, MV88E6123, MV88E6161, and MV88E6165. Patch 09/15 and 10/15 add support for EEPROM access to the DSA subsystem. Patch 11/15 implements EEPROM access for MV88E6352 and MV88E6176. Patch 12/15 adds support for reading switch registers to the DSA subsystem. Patches 13/15 amd 14/15 implement support for reading switch registers to the drivers for MV88E6352, MV88E6176, MV88E6123, MV88E6161, and MV88E6165. Patch 15/15 adds support for reading additional RMON registers to the drivers for MV88E6352, MV88E6176, MV88E6123, MV88E6161, and MV88E6165. The series was tested on top of v3.18-rc2 in an x86 system with MV88E6352. Testing in systems with 88E6131, 88E6060 and MV88E6165 was done earlier (I don't have access to those systems right now). The series was also build tested using my build system at http://server.roeck-us.net:8010/builders. Look into the 'dsa' column for build results. The series merges cleanly into net-next as of today (10/29). v3: - Fix bug in eeprom patches seen if devicetree is enabled: eeprom-length property is attached to switch devicetree node, not to dsa node, and there was a compile error. v2: - Made reporting chip temperatures through the hwmon subsystem optional with new Kconfig option - Changed the hwmon chip name to <network device name>_dsa<index> - Made EEPROM presence and size configurable through platform and devicetree data - Various minor changes and fixes (see individual patches for details) ==================== Reviewed-by:
Florian Fainelli <f.fainelli@gmail.com> Signed-off-by:
-
Guenter Roeck authored
Display sw_in_discards, sw_in_filtered, and sw_out_filtered for chips supported by mv88e6123_61_65 and mv88e6352 drivers. The variables are provided in port registers, not the normal status registers. Mark by adding 0x100 to the register offset and add special handling code to mv88e6xxx_get_ethtool_stats. Signed-off-by:
Guenter Roeck <linux@roeck-us.net> Signed-off-by:
-
Guenter Roeck authored
Report switch register values to ethtool. Signed-off-by:
-
Guenter Roeck authored
The infrastructure can now report switch registers to ethtool. Add support for it to the mv88e6123_61_65 driver. Signed-off-by:
-
Guenter Roeck authored
Add support for reading switch registers with 'ethtool -d'. Signed-off-by:
-
Guenter Roeck authored
MV88E6352 supports read and write access to its configuration eeprom. There is no means to detect if an EEPROM is connected to the switch. Also, the switch supports EEPROMs with different sizes, but can not detect or report the type or size of connected EEPROMs. Therefore, do not implement the get_eeprom_len callback but depend on platform or devicetree data to provide information about EEPROM presence and size. Signed-off-by:
-
Guenter Roeck authored
The dsa core now supports reading from and writing to a switch EEPROM if connected. Describe optional devicetree property indicating that an EEPROM is present and its size. Signed-off-by:
-
Guenter Roeck authored
On some chips it is possible to access the switch eeprom. Add infrastructure support for it. Signed-off-by:
-
Guenter Roeck authored
MV88E6123 and compatible chips support reading the chip temperature from PHY register 6:26. Signed-off-by:
-
Guenter Roeck authored
MV88E6352 supports reading the chip temperature from two PHY registers, 6:26 and 6:27. Report it using the more accurate register 6:27. Also report temperature limit and alarm. Signed-off-by:
-
Guenter Roeck authored
Some switches provide chip temperature data. Add support for reporting it through the hwmon subsystem. Signed-off-by:
-
Guenter Roeck authored
MV88E6176 is mostly compatible to MV88E6352 and is documented in the same functional specification. Add support for it. Signed-off-by:
-
Guenter Roeck authored
Marvell 88E6352 is mostly compatible to MV88E6123/61/65, but requires indirect phy access. Also, its configuration registers are a bit different. Signed-off-by:
-
Guenter Roeck authored
Report known silicon revisions when probing Marvell 88E6131 switches. Signed-off-by:
-
Guenter Roeck authored
Report known silicon revisions when probing Marvell 88E6060 switches. Signed-off-by:
-
Guenter Roeck authored
Setting skb->protocol to a private protocol type may result in warning messages such as e1000e 0000:00:19.0 em1: checksum_partial proto=dada! This happens if the L3 protocol is IP or IPv6 and skb->ip_summed is set to CHECKSUM_PARTIAL. Looking through the code, it appears that changing skb->protocol for transmitted packets is not necessary and may actually be harmful. For example, it prevents purposely unmodified (from a DSA perspective) network drivers from properly setting up their transmit checksum offload pointers since they inspect skb->protocol to set up the IPv4 header or IPv6 header pointers. So don't unnecessarily change the protocol field. Signed-off-by:
-
- 29 Oct, 2014 11 commits
-
-
Nicolas Dichtel authored
In neigh_parms_release() we loop over all entries to find the entry given in argument and being able to remove it from the list. By using a double linked list, we can avoid this loop. Here are some numbers with 30 000 dummy interfaces configured: Before the patch: $ time rmmod dummy real 2m0.118s user 0m0.000s sys 1m50.048s After the patch: $ time rmmod dummy real 1m9.970s user 0m0.000s sys 0m47.976s Suggested-by:
Thierry Herbelot <thierry.herbelot@6wind.com> Signed-off-by:
Nicolas Dichtel <nicolas.dichtel@6wind.com> Acked-by:
-
Eric Dumazet authored
napi_schedule() can be called from any context and has to mask hard irqs. Add a variant that can only be called from hard interrupts handlers or when irqs are already masked. Many NIC drivers can use it from their hard IRQ handler instead of generic variant. Signed-off-by:
-
David S. Miller authored
David Vrabel says: ==================== xen-netback: minor cleanups Two minor xen-netback cleanups originally from Zoltan. ==================== Signed-off-by: -
Zoltan Kiss authored
This flag is unnecessary, it came from some old code. Suggested-by:
Eric Dumazet <eric.dumazet@gmail.com> Signed-off-by:
Zoltan Kiss <zoltan.kiss@linaro.org> Signed-off-by:
David Vrabel <david.vrabel@citrix.com> Acked-by:
Wei Liu <wei.liu2@citrix.com> Signed-off-by:
-
Zoltan Kiss authored
Otherwise the interrupt handler still calls napi_complete. Although it won't schedule NAPI again as either NAPI_STATE_DISABLE or NAPI_STATE_SCHED is set, it is just unnecessary, and it makes more sense to do this way. Signed-off-by:
-
Erik Kline authored
Add a sysctl that causes an interface's optimistic addresses to be considered equivalent to other non-deprecated addresses for source address selection purposes. Preferred addresses will still take precedence over optimistic addresses, subject to other ranking in the source address selection algorithm. This is useful where different interfaces are connected to different networks from different ISPs (e.g., a cell network and a home wifi network). The current behaviour complies with RFC 3484/6724, and it makes sense if the host has only one interface, or has multiple interfaces on the same network (same or cooperating administrative domain(s), but not in the multiple distinct networks case. For example, if a mobile device has an IPv6 address on an LTE network and then connects to IPv6-enabled wifi, while the wifi IPv6 address is undergoing DAD, IPv6 connections will try use the wifi default route with the LTE IPv6 address, and will get stuck until they time out. Also, because optimistic nodes can receive frames, issue an RTM_NEWADDR as soon as DAD starts (with the IFA_F_OPTIMSTIC flag appropriately set). A second RTM_NEWADDR is sent if DAD completes (the address flags have changed), otherwise an RTM_DELADDR is sent. Also: add an entry in ip-sysctl.txt for optimistic_dad. Signed-off-by:
Erik Kline <ek@google.com> Acked-by:
Lorenzo Colitti <lorenzo@google.com> Acked-by:
Hannes Frederic Sowa <hannes@stressinduktion.org> Signed-off-by:
-
David S. Miller authored
Hayes Wang says: ==================== r8152: support nway_reset Fix the CHECK from checkpatch.pl and support nway_reset. ==================== Signed-off-by: -
hayeswang authored
Support the nway_reset() function for ethtool. Signed-off-by:
Hayes Wang <hayeswang@realtek.com> Signed-off-by:
-
hayeswang authored
Replace tx_underun with tx_underrun for checkpatch.pl. Signed-off-by:
-
Eric Dumazet authored
While testing upcoming Yaogong patch (converting out of order queue into an RB tree), I hit the max reordering level of linux TCP stack. Reordering level was limited to 127 for no good reason, and some network setups [1] can easily reach this limit and get limited throughput. Allow a new max limit of 300, and add a sysctl to allow admins to even allow bigger (or lower) values if needed. [1] Aggregation of links, per packet load balancing, fabrics not doing deep packet inspections, alternative TCP congestion modules... Signed-off-by:
-
Roberto Medina authored
Several warnings and errors of coding style rules corrected. Compile tested. Signed-off-by:
Roberto Medina <robertoxmed@gmail.com> Signed-off-by:
-
