[PATCH net-next] liquidio: moved console_bitmask module param to lio_main.c

From: Intiyaz Basha Moving PF module param console_bitmask to lio_main.c for consistency. Signed-off-by: Intiyaz Basha Signed-off-by: Felix Manlunas --- drivers/net/ethernet/cavium/liquidio/lio_main.c | 15

Re: [PATCH V6 net-next 0/8] Hisilicon Network Subsystem 3 Ethernet Driver

From: Salil Mehta Date: Wed, 2 Aug 2017 16:59:44 +0100 > This patch-set contains the support of the HNS3 (Hisilicon Network Subsystem > 3) > Ethernet driver for hip08 family of SoCs and future upcoming SoCs. ... Series applied, thanks.

Re: [PATCH v2 net 0/3] tcp: fix xmit timer rearming to avoid stalls

From: Neal Cardwell Date: Thu, 3 Aug 2017 09:19:51 -0400 > This patch series is a bug fix for a TCP loss recovery performance bug > reported independently in recent netdev threads: > > (i) July 26, 2017: netdev thread "TCP fast retransmit issues" > (ii) July 26,

Re: [PATCH v7 net-next] net: systemport: Support 64bit statistics

On 08/03/2017 04:16 PM, Stephen Hemminger wrote: > On Fri, 4 Aug 2017 00:07:45 +0100 > "Jianming.qiao" wrote: > >> static const struct bcm_sysport_stats bcm_sysport_gstrings_stats[] = { >> /* general stats */ >> -STAT_NETDEV(rx_packets), >> -

[PATCH 1/2 net-next] tcp: fix cwnd undo in Reno and HTCP congestion controls

Using ssthresh to revert cwnd is less reliable when ssthresh is bounded to 2 packets. This patch uses an existing variable in TCP "prior_cwnd" that snapshots the cwnd right before entering fast recovery and RTO recovery in Reno. This fixes the issue discussed in netdev thread: "A buggy behavior

[PATCH 2/2 net-next] tcp: consolidate congestion control undo functions

Most TCP congestion controls are using identical logic to undo cwnd except BBR. This patch consolidates these similar functions to the one used currently by Reno and others. Suggested-by: Neal Cardwell Signed-off-by: Yuchung Cheng Signed-off-by: Neal

Re: [PATCH net-next v3 1/2] bpf: add support for sys_enter_* and sys_exit_* tracepoints

On 8/3/17 6:29 AM, Yonghong Song wrote: @@ -578,8 +596,9 @@ static void perf_syscall_enter(void *ignore, struct pt_regs *regs, long id) if (!sys_data) return; + prog = READ_ONCE(sys_data->enter_event->prog); head =

Re: [RFC PATCH 4/6] net: sockmap with sk redirect support

On 08/03/2017 09:22 PM, Tom Herbert wrote: > On Thu, Aug 3, 2017 at 4:37 PM, John Fastabend > wrote: >> Recently we added a new map type called dev map used to forward XDP >> packets between ports (6093ec2dc313). This patches introduces a >> similar notion for sockets.

Re: [RFC PATCH 4/6] net: sockmap with sk redirect support

On 08/03/2017 09:22 PM, Tom Herbert wrote: > On Thu, Aug 3, 2017 at 4:37 PM, John Fastabend > wrote: >> Recently we added a new map type called dev map used to forward XDP >> packets between ports (6093ec2dc313). This patches introduces a >> similar notion for sockets.

[net-next PATCH] net: comment fixes against BPF devmap helper calls

Update BPF comments to accurately reflect XDP usage. Fixes: 97f91a7cf04ff ("bpf: add bpf_redirect_map helper routine") Reported-by: Alexei Starovoitov Signed-off-by: John Fastabend --- include/uapi/linux/bpf.h | 16 +++- 1 file changed,

RE: [PATCH V6 net-next 0/8] Hisilicon Network Subsystem 3 Ethernet Driver

Thanks a ton, Dave! > -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Thursday, August 03, 2017 11:10 PM > To: Salil Mehta > Cc: Zhuangyuzeng (Yisen); huangdaode; lipeng (Y); > mehta.salil@gmail.com; netdev@vger.kernel.org; linux- > ker...@vger.kernel.org;

[PATCH net-next] net: dsa: User per-cpu 64-bit statistics

During testing with a background iperf pushing 1Gbit/sec worth of traffic and having both ifconfig and ethtool collect statistics, we could see quite frequent deadlocks. Convert the often accessed DSA slave network devices statistics to per-cpu 64-bit statistics to remove these deadlocks and

Re: Gift-

Good Day, My wife and I have awarded you with a donation of $ 1,000,000.00 Dollars from part of our Jackpot Lottery of 50 Million Dollars, respond with your details for claims. We await your earliest response and God Bless you. Friedrich And Annand Mayrhofer. --- This email has been checked

Re: [PATCH net-next v3 1/2] bpf: add support for sys_enter_* and sys_exit_* tracepoints

On Thu, Aug 3, 2017 at 7:08 PM, Alexei Starovoitov wrote: > On 8/3/17 6:29 AM, Yonghong Song wrote: >> >> @@ -578,8 +596,9 @@ static void perf_syscall_enter(void *ignore, struct >> pt_regs *regs, long id) >> if (!sys_data) >> return; >> >> + prog =

[PATCH 1/2 v2 net-next] tcp: fix cwnd undo in Reno and HTCP congestion controls

Using ssthresh to revert cwnd is less reliable when ssthresh is bounded to 2 packets. This patch uses an existing variable in TCP "prior_cwnd" that snapshots the cwnd right before entering fast recovery and RTO recovery in Reno. This fixes the issue discussed in netdev thread: "A buggy behavior

[PATCH 0/2 v2 net-next] tcp cwnd undo refactor

This patch series consolidate similar cwnd undo functions implemented by various congestion control by using existing tcp socket state variable. The first patch fixes a corner case in of cwnd undo in Reno and HTCP. Since the bug has existed for many years and is very minor, we consider this patch

[PATCH 2/2 v2 net-next] tcp: consolidate congestion control undo functions

Most TCP congestion controls are using identical logic to undo cwnd except BBR. This patch consolidates these similar functions to the one used currently by Reno and others. Suggested-by: Neal Cardwell Signed-off-by: Yuchung Cheng Signed-off-by: Neal

Re: [PATCH] PCI: Update ACS quirk for more Intel 10G NICs

On Thu, 3 Aug 2017 16:49:11 -0500 Bjorn Helgaas wrote: > On Thu, Jul 20, 2017 at 02:41:01PM -0700, Roland Dreier wrote: > > From: Roland Dreier > > > > Add one more variant of the 82599 plus the device IDs for X540 and X550 > > variants. Intel has

Re: [PATCH net-next v2 0/7] net: mvpp2: add TX interrupts support

From: Thomas Petazzoni Date: Thu, 3 Aug 2017 10:41:54 +0200 > So far, the mvpp2 driver was using an hrtimer to handle TX > completion. This patch series adds support for using TX interrupts > (for each CPU) on PPv2.2, the variant of the IP used on Marvell

Re: [iproute PATCH] iplink: Notify user if EEXIST error might be spurious

On Tue, 1 Aug 2017 19:27:47 +0200 Phil Sutter wrote: > Back in the days when RTM_NEWLINK wasn't yet implemented, people had to > rely upon kernel modules to create (virtual) interfaces for them. The > number of those was usually defined via module parameter, and a sane > default

[PATCH v7 net-next] net: systemport: Support 64bit statistics

When using Broadcom Systemport device in 32bit Platform, ifconfig can only report up to 4G tx,rx status, which will be wrapped to 0 when the number of incoming or outgoing packets exceeds 4G, only taking around 2 hours in busy network environment (such as streaming). Therefore, it makes hard for

[RFC PATCH 0/6] BPF socket redirect

This series implements socket redirect for BPF using XDP redirect as a model. The user flow and internals are similar in many ways. First we add a new map type called, sockmap. A sockmap holds references to sock structs. Next a bpf helper call is added to support redirect between sockets,

Re: [patch net-next 00/21] mlxsw: Support for IPv6 UC router

From: Jiri Pirko Date: Thu, 3 Aug 2017 13:28:10 +0200 > This set adds support for IPv6 unicast routes offload. Series applied, thanks.

Re: [patch net-next 00/21] mlxsw: Support for IPv6 UC router

From: David Ahern Date: Thu, 3 Aug 2017 16:39:54 -0600 > On 8/3/17 4:36 PM, David Miller wrote: >> From: Jiri Pirko >> Date: Thu, 3 Aug 2017 13:28:10 +0200 >> >>> This set adds support for IPv6 unicast routes offload. >> >> Series applied, thanks. >> >

Re: [PATCH V3 net-next 02/21] net-next/hinic: Initialize hw device components

From: Aviad Krawczyk Date: Thu, 3 Aug 2017 17:54:08 +0800 > +static int get_capability(struct hinic_hwdev *hwdev, > + struct hinic_dev_cap *dev_cap) > +{ > + struct hinic_hwif *hwif = hwdev->hwif; > + struct hinic_cap *nic_cap = >nic_cap;

Re: [PATCH v4] ss: Enclose IPv6 address in brackets

On Tue, 1 Aug 2017 18:54:33 +0200 Florian Lehner wrote: > - if (a->family == AF_INET) { > - if (a->data[0] == 0) { > + if (a->data[0] == 0) { > buf[0] = '*'; > buf[1] = 0; This won't work right with IPv6 you need

Re: [PATCH v3 net-next 4/4] ulp: Documention for ULP infrastructure

On Thu, 3 Aug 2017, Tom Herbert wrote: Add a doc in Documentation/networking Signed-off-by: Tom Herbert --- Documentation/networking/ulp.txt | 82 1 file changed, 82 insertions(+) create mode 100644 Documentation/networking/ulp.txt

Re: [PATCH v7 net-next] net: systemport: Support 64bit statistics

From: Florian Fainelli Date: Thu, 3 Aug 2017 16:20:04 -0700 > On 08/03/2017 04:16 PM, Stephen Hemminger wrote: >> On Fri, 4 Aug 2017 00:07:45 +0100 >> "Jianming.qiao" wrote: >> >>> static const struct bcm_sysport_stats bcm_sysport_gstrings_stats[] =

Re: [PATCH] PCI: Update ACS quirk for more Intel 10G NICs

On Thu, Jul 20, 2017 at 02:41:01PM -0700, Roland Dreier wrote: > From: Roland Dreier > > Add one more variant of the 82599 plus the device IDs for X540 and X550 > variants. Intel has confirmed that none of these devices does peer-to-peer > between functions. The X540

Re: [PATCH] net: arc_emac: Add support for ndo_do_ioctl net_device_ops operation

From: Romain Perier Date: Thu, 3 Aug 2017 09:49:03 +0200 > This operation is required for handling ioctl commands like SIOCGMIIREG, > when debugging MDIO registers from userspace. > > This commit adds support for this operation. > > Signed-off-by: Romain Perier

Re: [PATCH V3 net-next 03/21] net-next/hinic: Initialize api cmd resources

From: Aviad Krawczyk Date: Thu, 3 Aug 2017 17:54:09 +0800 > +static int alloc_cmd_buf(struct hinic_api_cmd_chain *chain, > + struct hinic_api_cmd_cell *cell, int cell_idx) > +{ > + struct hinic_hwif *hwif = chain->hwif; > + struct pci_dev

Re: [iproute PATCH] bpf: Make bytecode-file reading a little more robust

On Wed, 2 Aug 2017 14:57:56 +0200 Phil Sutter wrote: > bpf_parse_string() will now correctly handle: > > - Extraneous whitespace, > - OPs on multiple lines and > - overlong file names. > > The added feature of allowing to have OPs on multiple lines (like e.g. > tcpdump prints

Re: [iproute PATCH] tc-simple: Fix documentation

On Thu, 3 Aug 2017 17:00:51 +0200 Phil Sutter wrote: > - CONTROL has to come last, otherwise 'index' applies to gact and not > simple itself. > - Man page wasn't updated to reflect syntax changes. > > Signed-off-by: Phil Sutter Applid, thanks Phil

Re: [PATCH iproute2] netns: make /var/run/netns bind-mount recursive

On Tue, 1 Aug 2017 17:46:09 +0200 Casey Callendrello wrote: > When ip netns {add|delete} is first run, it bind-mounts /var/run/netns > on top of itself, then marks it as shared. However, if there are already > bind-mounts in the directory from other tools, these

Re: [PATCH 3/5] net: stmmac: Add Adaptrum Anarion GMAC glue layer

On Mon, Jul 31, 2017 at 08:11:00AM -0700, Alex wrote: > Hi David, > > On 07/28/2017 07:01 PM, David Miller wrote: > > From: Alexandru Gagniuc > > Date: Fri, 28 Jul 2017 15:07:03 -0700 > > > > > Before the GMAC on the Anarion chip can be used, the PHY interface > > >

[RFC PATCH 6/6] net: sockmap sample program

This program binds a program to a cgroup and then matches hard coded IP addresses and adds these to a sockmap. This will receive messages from the backend and send them to the client. client:X <---> frontend:1 client:X <---> backend:80 To keep things simple this is only designed for

Re: Gift-

Good Day, My wife and I have awarded you with a donation of $ 1,000,000.00 Dollars from part of our Jackpot Lottery of 50 Million Dollars, respond with your details for claims. We await your earliest response and God Bless you. Friedrich And Annand Mayrhofer. --- This email has been checked

[PATCH] MIPS: Add missing file for eBPF JIT.

Inexplicably, commit f381bf6d82f0 ("MIPS: Add support for eBPF JIT.") lost a file somewhere on its path to Linus' tree. Add back the missing ebpf_jit.c so that we can build with CONFIG_BPF_JIT selected. This version of ebpf_jit.c is identical to the original except for two minor change need to

Re: [PATCH 2/2 net-next] tcp: consolidate congestion control undo functions

Hi Yuchung, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Yuchung-Cheng/tcp-fix-cwnd-undo-in-Reno-and-HTCP-congestion-controls/20170804-085255 config: xtensa-allmodconfig (attached as .config) compiler: xtensa-linux-gcc (GCC) 4.9.0 reproduce:

Re: [PATCH net-next v2 00/13] Change DSA's FDB API and perform switchdev cleanup

[...] >> Now we have the "offload" read only flag, which is good to inform about >> a successfully programmed hardware, but adds another level of complexity >> to understand the interaction with the hardware. >> >> I think iproute2 is getting more and more confusing. From what I >> understood,

Re: [patch net-next 00/21] mlxsw: Support for IPv6 UC router

On 8/3/17 4:36 PM, David Miller wrote: > From: Jiri Pirko > Date: Thu, 3 Aug 2017 13:28:10 +0200 > >> This set adds support for IPv6 unicast routes offload. > > Series applied, thanks. > I take it you disagree with my comment on patch 10 about the RTF_OFFLOAD flag? that is

Re: [patch net-next 00/21] mlxsw: Support for IPv6 UC router

On 8/3/17 4:41 PM, David Miller wrote: > But unlike the percpu flag, don't we want to somehow propagate offload > state to the user? It's a per nexthop flag. For IPv4 it is tracked in fib_nh.nh_flags. Perhaps it is time for rt6_info to have nh_flags as well. > > I'm sure whatever we decide Jiri

Re: [iproute PATCH] Really fix get_addr() and get_prefix() error messages

On Tue, 1 Aug 2017 18:36:11 +0200 Phil Sutter wrote: > Both functions take the desired address family as a parameter. So using > that to notify the user what address family was expected is correct, > unlike using dst->family which will tell the user only what address > family was

Re: [PATCH v7 net-next] net: systemport: Support 64bit statistics

On Fri, 4 Aug 2017 00:07:45 +0100 "Jianming.qiao" wrote: > static const struct bcm_sysport_stats bcm_sysport_gstrings_stats[] = { > /* general stats */ > - STAT_NETDEV(rx_packets), > - STAT_NETDEV(tx_packets), > - STAT_NETDEV(rx_bytes), > -

Re: [PATCH v3 net-next 2/4] sock: ULP infrastructure

On Thu, 3 Aug 2017, Tom Herbert wrote: Generalize the TCP ULP infrastructure recently introduced to support kTLS. This adds a SO_ULP socket option and creates new fields in sock structure for ULP ops and ULP data. Also, the interface allows additional per ULP parameters to be set so that a ULP

Re: [PATCH 3/5] net: stmmac: Add Adaptrum Anarion GMAC glue layer

On Fri, Jul 28, 2017 at 03:07:03PM -0700, Alexandru Gagniuc wrote: > Before the GMAC on the Anarion chip can be used, the PHY interface > selection must be configured with the DWMAC block in reset. > > This layer covers a block containing only two registers. Although it > is possible to model

[RFC PATCH 4/6] net: sockmap with sk redirect support

Recently we added a new map type called dev map used to forward XDP packets between ports (6093ec2dc313). This patches introduces a similar notion for sockets. A sockmap allows users to add participating sockets to a map. When sockets are added to the map enough context is stored with the map

[RFC PATCH 5/6] net: bpf, add skb to sk lookup routines

Add some useful skb to sk routines to fine ports on a connected socket. This is for testing, we may prefer to put sk in bpf sk_buff representation and access these fields directly. Similar to sock ops ctx access. Signed-off-by: John Fastabend ---

[RFC PATCH 3/6] net: fixes for skb_send_sock

A couple fixes to new skb_send_sock infrastructure. However, no users currently exist for this code (adding user in next handful of patches) so it should not be possible to trigger a panic with in-kernel code. Fixes: 306b13eb3cf9 ("proto_ops: Add locked held versions of sendmsg and sendpage")

[RFC PATCH 1/6] net: early init support for strparser

It is useful to allow strparser to init sockets before the read_sock callback has been established. Signed-off-by: John Fastabend --- net/strparser/strparser.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/net/strparser/strparser.c

[RFC PATCH 2/6] net: add sendmsg_locked and sendpage_locked to af_inet6

To complete the sendmsg_locked and sendpage_locked implementation add the hooks for af_inet6 as well. Signed-off-by: John Fastabend --- net/ipv6/af_inet6.c |2 ++ 1 file changed, 2 insertions(+) diff --git a/net/ipv6/af_inet6.c b/net/ipv6/af_inet6.c index

[PATCH net 1/1] netvsc: fix race on sub channel creation

The existing sub channel code did not wait for all the sub-channels to completely initialize. This could lead to race causing crash in napi_netif_del() from bad list. The existing code would send an init message, then wait only for the initial response that the init message was received. It

[PATCH net 0/1] netvsc: race on sub channel open

Found this while testing mtu, queue and buffer size changes in 4.13, but the problem goes back much further. The addition of NAPI makes the race into a crash. Before that there was just a risk of sending on an uninitialized channel. Stephen Hemminger (1): netvsc: fix race on sub channel

Re: [PATCH net-next] net: dsa: User per-cpu 64-bit statistics

On Thu, 2017-08-03 at 21:33 -0700, Florian Fainelli wrote: > During testing with a background iperf pushing 1Gbit/sec worth of > traffic and having both ifconfig and ethtool collect statistics, we > could see quite frequent deadlocks. Convert the often accessed DSA slave > network devices

Re: [PATCH net-next v2 00/13] Change DSA's FDB API and perform switchdev cleanup

Fri, Aug 04, 2017 at 12:39:02AM CEST, arka...@mellanox.com wrote: > >[...] > >>> Now we have the "offload" read only flag, which is good to inform about >>> a successfully programmed hardware, but adds another level of complexity >>> to understand the interaction with the hardware. >>> >>> I think

[PATCH] samples/bpf: Fix cross compiler error with bpf sample

When cross-compiling the bpf sample map_perf_test for aarch64, I find that __NR_getpgrp is undefined. This causes build errors. Fix it by allowing the deprecated syscall in the sample. Signed-off-by: Joel Fernandes --- samples/bpf/map_perf_test_user.c | 2 ++ 1 file changed,

Re: [PATCH v3 net-next 3/5] net: dsa: lan9303: Simplify lan9303_xxx_packet_processing() usage

On Thu, Aug 03, 2017 at 11:45:05AM +0200, Egil Hjelmeland wrote: > Simplify usage of lan9303_enable_packet_processing, > lan9303_disable_packet_processing() > > Signed-off-by: Egil Hjelmeland Reviewed-by: Andrew Lunn Andrew

Re: [PATCH v3 net-next 1/5] net: dsa: lan9303: Change lan9303_xxx_packet_processing() port param.

On Thu, Aug 03, 2017 at 11:45:03AM +0200, Egil Hjelmeland wrote: > lan9303_enable_packet_processing, lan9303_disable_packet_processing() > Pass port number (0,1,2) as parameter instead of port offset. > Because other functions in the module pass port numbers. > And to enable simplifications in

Re: [PATCH v3 net-next 2/5] net: dsa: lan9303: define LAN9303_NUM_PORTS 3

On Thu, Aug 03, 2017 at 11:45:04AM +0200, Egil Hjelmeland wrote: > Will be used instead of '3' in upcomming patches. > > Signed-off-by: Egil Hjelmeland Signed-off-by: Andrew Lunn Andrew

Re: [PATCH v3 net-next 4/5] net: dsa: lan9303: Rename lan9303_xxx_packet_processing()

On Thu, Aug 03, 2017 at 11:45:06AM +0200, Egil Hjelmeland wrote: > The lan9303_enable_packet_processing, lan9303_disable_packet_processing > functions operate on port, so the names should reflect that. > And to align with lan9303_disable_processing(), rename: > > lan9303_enable_packet_processing

Re: [PATCH v3 net-next 5/5] net: dsa: lan9303: refactor lan9303_get_ethtool_stats

On Thu, Aug 03, 2017 at 11:45:07AM +0200, Egil Hjelmeland wrote: > In lan9303_get_ethtool_stats: Get rid of 0x400 constant magic > by using new lan9303_read_switch_reg() inside loop. > Reduced scope of two variables. > > Signed-off-by: Egil Hjelmeland Reviewed-by:

Re: [PATCH v2 net-next 2/3] net: dsa: lan9303: define LAN9303_NUM_PORTS 3

> Related question: If the driver does dsa_switch_alloc(3), can it then > trust that all "port" params passed in DSA methods will be between > 0 and 2? Yes. Andrew

[PATCH v8 4/4] net/cxgb4vf: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

From: Casey Leedom cxgb4vf Ethernet driver now queries PCIe configuration space to determine if it can send TLPs to it with the Relaxed Ordering Attribute set, just like the pf did. Signed-off-by: Casey Leedom Signed-off-by: Ding Tianhong

[PATCH v8 3/4] net/cxgb4: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

From: Casey Leedom cxgb4 Ethernet driver now queries PCIe configuration space to determine if it can send TLPs to it with the Relaxed Ordering Attribute set. Remove the enable_pcie_relaxed_ordering() to avoid enable PCIe Capability Device Control[Relaxed Ordering Enable] at

[PATCH v8 0/4] Add new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

Some devices have problems with Transaction Layer Packets with the Relaxed Ordering Attribute set. This patch set adds a new PCIe Device Flag, PCI_DEV_FLAGS_NO_RELAXED_ORDERING, a set of PCI Quirks to catch some known devices with Relaxed Ordering issues, and a use of this new flag by the cxgb4

[PATCH v8 1/4] PCI: Add new PCIe Fabric End Node flag, PCI_DEV_FLAGS_NO_RELAXED_ORDERING

From: Casey Leedom The patch adds a new flag PCI_DEV_FLAGS_NO_RELAXED_ORDERING to indicate that Relaxed Ordering (RO) attribute should not be used for Transaction Layer Packets (TLP) targetted towards these affected root complexes. Current list of affected parts include Intel

[PATCH v8 2/4] PCI: Disable PCIe Relaxed Ordering if unsupported

When bit4 is set in the PCIe Device Control register, it indicates whether the device is permitted to use relaxed ordering. On some platforms using relaxed ordering can have performance issues or due to erratum can cause data-corruption. In such cases devices must avoid using relaxed ordering.

Re: [PATCH net-next v2 1/2] bpf: add support for sys_enter_* and sys_exit_* tracepoints

Hi Yonghong, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Yonghong-Song/bpf-add-support-for-sys_-enter-exit-_-tracepoints/20170803-213504 config: i386-randconfig-x019-201731 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901

[PATCH v2 net 2/3] tcp: enable xmit timer fix by having TLP use time when RTO should fire

Have tcp_schedule_loss_probe() base the TLP scheduling decision based on when the RTO *should* fire. This is to enable the upcoming xmit timer fix in this series, where tcp_schedule_loss_probe() cannot assume that the last timer installed was an RTO timer (because we are no longer doing the "rearm

[PATCH v2 net 3/3] tcp: fix xmit timer to only be reset if data ACKed/SACKed

Fix a TCP loss recovery performance bug raised recently on the netdev list, in two threads: (i) July 26, 2017: netdev thread "TCP fast retransmit issues" (ii) July 26, 2017: netdev thread: "[PATCH V2 net-next] TLP: Don't reschedule PTO when there's one outstanding TLP retransmission"

[PATCH v2 net 1/3] tcp: introduce tcp_rto_delta_us() helper for xmit timer fix

Pure refactor. This helper will be required in the xmit timer fix later in the patch series. (Because the TLP logic will want to make this calculation.) Fixes: 6ba8a3b19e76 ("tcp: Tail loss probe (TLP)") Signed-off-by: Neal Cardwell Signed-off-by: Yuchung Cheng

[PATCH v2 net 0/3] tcp: fix xmit timer rearming to avoid stalls

This patch series is a bug fix for a TCP loss recovery performance bug reported independently in recent netdev threads: (i) July 26, 2017: netdev thread "TCP fast retransmit issues" (ii) July 26, 2017: netdev thread: "[PATCH V2 net-next] TLP: Don't reschedule PTO when there's one

[patch net-next 07/21] ipv6: fib: Add in-kernel notifications for route add / delete

From: Ido Schimmel As with IPv4, allow listeners of the FIB notification chain to receive notifications whenever a route is added, replaced or deleted. This is done by placing calls to the FIB notification chain in the two lowest level functions that end up performing these

[patch net-next 08/21] ipv6: fib_rules: Dump rules during registration to FIB chain

From: Ido Schimmel Allow users of the FIB notification chain to receive a complete view of the IPv6 FIB rules upon registration to the chain. The integrity of the dump is ensured by a per-family sequence counter that is incremented (under RTNL) whenever a rule is added or

[patch net-next 10/21] ipv6: fib: Add offload indication to routes

From: Ido Schimmel Allow user space applications to see which routes are offloaded and which aren't by setting the RTNH_F_OFFLOAD flag when dumping them. To be consistent with IPv4, offload indication is provided on a per-nexthop basis. Signed-off-by: Ido Schimmel

[patch net-next 09/21] ipv6: fib: Dump tables during registration to FIB chain

From: Ido Schimmel Dump all the FIB tables in each net namespace upon registration to the FIB notification chain so that the callee will have a complete view of the tables. The integrity of the dump is ensured by a per-table sequence counter that is incremented (under write

[patch net-next 05/21] ipv6: fib_rules: Check if rule is a default rule

From: Ido Schimmel As explained in commit 3c71006d15fd ("ipv4: fib_rules: Check if rule is a default rule"), drivers supporting IPv6 FIB offload need to be able to sanitize the rules they don't support and potentially flush their tables. Add an IPv6 helper to check if a FIB

[patch net-next 03/21] rocker: Ignore address families other than IPv4

From: Ido Schimmel As in previous patch, ignore IPv6 notifications since the driver doesn't support these. Signed-off-by: Ido Schimmel Signed-off-by: Jiri Pirko --- drivers/net/ethernet/rocker/rocker_main.c | 4 1 file

[patch net-next 01/21] net: core: Make the FIB notification chain generic

From: Ido Schimmel The FIB notification chain is currently soley used by IPv4 code. However, we're going to introduce IPv6 FIB offload support, which requires these notification as well. As explained in commit c3852ef7f2f8 ("ipv4: fib: Replay events when registering FIB

Re: [PATCH v3 2/4] dt-bindings: can: fixed-transceiver: Add new CAN fixed transceiver bindings

On 08/03/2017 04:18 AM, Sergei Shtylyov wrote: > Hello! > > On 8/3/2017 3:51 AM, Franklin S Cooper Jr wrote: > >> Add documentation to describe usage of the new fixed transceiver binding. >> This new binding is applicable for any CAN device therefore it exists as >> its own document. >> >>

Re: [PATCH v3 3/4] dt-bindings: can: m_can: Include reference to new fixed transceiver binding

On 08/03/2017 04:20 AM, Sergei Shtylyov wrote: > On 8/3/2017 3:51 AM, Franklin S Cooper Jr wrote: > >> Add information regarding fixed transceiver binding. This is especially >> important for MCAN since the IP allows CAN FD mode to run significantly >> faster than what most transceivers are

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

Mason writes: > IIUC, sender (desktop system) sends datagrams as fast as possible. > Receiver (tango board) drops around 24% of all datagrams. > I think this invalidates the theory that exhausting RX descriptors > wedges RX DMA. No, it doesn't. The bottleneck causing packet

[patch net-next 06/21] ipv6: fib: Add FIB notifiers callbacks

From: Ido Schimmel We're about to add IPv6 FIB offload support, so implement the necessary callbacks in IPv6 code, which will later allow us to add routes and rules notifications. Signed-off-by: Ido Schimmel Signed-off-by: Jiri Pirko

[patch net-next 04/21] net: fib_rules: Implement notification logic in core

From: Ido Schimmel Unlike the routing tables, the FIB rules share a common core, so instead of replicating the same logic for each address family we can simply dump the rules and send notifications from the core itself. To protect the integrity of the dump, a rules-specific

[patch net-next 02/21] mlxsw: spectrum_router: Ignore address families other than IPv4

From: Ido Schimmel We're about to add IPv6 notifications in the FIB notification chain, but the driver currently doesn't support these, so ignore them. Signed-off-by: Ido Schimmel Signed-off-by: Jiri Pirko ---

[patch net-next 18/21] mlxsw: spectrum_router: Add support for IPv6 routes addition / deletion

From: Ido Schimmel Allow directly connected and remote unicast IPv6 routes to be programmed to the device's tables. As with IPv4, identical routes - sharing the same destination prefix - are ordered in a FIB node according to their table ID and then the metric. While the

[patch net-next 17/21] mlxsw: spectrum_router: Sanitize IPv6 FIB rules

From: Ido Schimmel We only allow FIB offload in the presence of default rules or an l3mdev rule. In a similar fashion to IPv4 FIB rules, sanitize IPv6 rules. Signed-off-by: Ido Schimmel Signed-off-by: Jiri Pirko ---

[patch net-next 14/21] ipv6: Regenerate host route according to node pointer upon interface up

From: Ido Schimmel When an interface is brought back up, the kernel tries to restore the host routes tied to its permanent addresses. However, if the host route was removed from the FIB, then we need to reinsert it. This is done by releasing the current dst and allocating a

[patch net-next 11/21] ipv6: fib: Don't assume only nodes hold a reference on routes

From: Ido Schimmel The code currently assumes that only FIB nodes can hold a reference on routes. Therefore, after fib6_purge_rt() has run and the route is no longer present in any intermediate nodes, it's assumed that its reference count would be 1 - taken by the node where

[patch net-next 15/21] ipv6: fib: Add helpers to hold / drop a reference on rt6_info

From: Ido Schimmel Similar to commit 1c677b3d2828 ("ipv4: fib: Add fib_info_hold() helper") and commit b423cb10807b ("ipv4: fib: Export free_fib_info()") add an helper to hold a reference on rt6_info and export rt6_release() to drop it and potentially release the route.

[patch net-next 19/21] mlxsw: spectrum_router: Add support for route replace

From: Ido Schimmel In case we got a replace event, then the replaced route must exist. If the route isn't capable of multipath, then replace first matching non-multipath capable route. If the route is capable of multipath and matching multipath capable route is found, then

[patch net-next 12/21] ipv6: fib: Unlink replaced routes from their nodes

From: Ido Schimmel When a route is deleted its node pointer is set to NULL to indicate it's no longer linked to its node. Do the same for routes that are replaced. This will later allow us to test if a route is still in the FIB by checking its node pointer instead of its

Re: [049/102] ath10k: explicitly request exclusive reset control

Philipp Zabel wrote: > Commit a53e35db70d1 ("reset: Ensure drivers are explicit when requesting > reset lines") started to transition the reset control request API calls > to explicitly state whether the driver needs exclusive or shared reset > control behavior. Convert

[PATCH] hysdn: fix to a race condition in put_log_buffer

The synchronization type that was used earlier to guard the loop that deletes unused log buffers may lead to a situation that prevents any thread from going through the loop. The patch deletes previously used synchronization mechanism and moves the loop under the spin_lock so the similar cases

Re: [PATCH] hysdn: fix to a race condition in put_log_buffer

Hello! On 08/03/2017 02:33 PM, Anton Volkov wrote: The synchronization type that was used earlier to guard the loop that deletes unused log buffers may lead to a situation that prevents any thread from going through the loop. The patch deletes previously used synchronization mechanism and

Re: [RFC PATCH v2 0/2] nb8800 suspend/resume support

Mason writes: > On 02/08/2017 19:31, Mason wrote: > >> # iperf3 -c 172.27.64.45 -u -b 950M >> Connecting to host 172.27.64.45, port 5201 >> [ 4] local 172.27.64.1 port 55533 connected to 172.27.64.45 port 5201 >> [ ID] Interval Transfer Bandwidth Total

Re: [PATCH v3 2/4] dt-bindings: can: fixed-transceiver: Add new CAN fixed transceiver bindings

On 08/03/2017 12:48 PM, Franklin S Cooper Jr wrote: Add documentation to describe usage of the new fixed transceiver binding. This new binding is applicable for any CAN device therefore it exists as its own document. Signed-off-by: Franklin S Cooper Jr ---

[patch net-next 13/21] ipv6: Regenerate host route according to node pointer upon loopback up

From: Ido Schimmel When the loopback device is brought back up we need to check if the host route attached to the address is still in the FIB and regenerate one in case it's not. Host routes using the loopback device are always inserted into and removed from the FIB under

[patch net-next 16/21] mlxsw: spectrum_router: Demultiplex FIB event based on family

From: Ido Schimmel The FIB notification block currently only handles IPv4 events, but we want to start handling IPv6 events soon, so lay the groundwork now. Do that by preparing the work item and process it according to the notified address family. Signed-off-by: Ido

[patch net-next 21/21] mlxsw: spectrum_router: Don't ignore IPv6 notifications

From: Ido Schimmel We now have all the necessary IPv6 infrastructure in place, so stop ignoring these notifications. Signed-off-by: Ido Schimmel Signed-off-by: Jiri Pirko --- drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c |

<    1   2   3   4   >