Re: [PATCH net-next] openvswitch: Make metadata_dst tunnel work in IP_TUNNEL_INFO_BRIDGE mode

On 2019/3/24 上午5:39, Pravin Shelar wrote: > On Sat, Mar 23, 2019 at 2:18 AM wenxu wrote: >> On 2019/3/23 下午3:50, Pravin Shelar wrote: >> >> On Thu, Mar 21, 2019 at 3:34 AM wrote: >> >> From: wenxu >> >> There is currently no support for the multicasti/broadcst aspects >> of VXLAN in ovs. In the

Re: [patch net-next v2 11/15] nfp: move devlink port type set after netdev registration

Sun, Mar 24, 2019 at 04:04:05AM CET, jakub.kicin...@netronome.com wrote: >On Sat, 23 Mar 2019 23:47:50 +0100, Jiri Pirko wrote: >> >type setting. I'd rather those calls happened on fully initialized >> >netdev (and port), could you perhaps just take this patch into the >> >> I don't get it, you

Re: [PATCH net-next 1/3] net: phy: aquantia: report remote capabilities if link partner is Aquantia PHY

On 24.03.2019 02:01, Florian Fainelli wrote: > > > On 3/23/2019 6:14 AM, Heiner Kallweit wrote: >> If both link partners are Aquantia PHY's then additional information is >> exchanged as part of the auto-negotiation. Report remote capabilities >> if link partner is Aquantia PHY. >> >> Signed-off-

Re: [PATCH net-next 2/3] net: phy: aquantia: report PHY details like firmware version

On 24.03.2019 02:04, Florian Fainelli wrote: > > > On 3/23/2019 6:15 AM, Heiner Kallweit wrote: >> Add reporting firmware details. These details are available only once >> the firmware has finished initializing the chip. This can take some >> time and we need to poll for init completion. >> >> Si

[PATCH v2 net-next] net: phy: aquantia: simplify aqr_config_intr

Simplify aqr_config_intr(). v2: - fix typo in subject and commit message Signed-off-by: Heiner Kallweit --- drivers/net/phy/aquantia_main.c | 45 ++--- 1 file changed, 13 insertions(+), 32 deletions(-) diff --git a/drivers/net/phy/aquantia_main.c b/drivers/net/phy/a

[PATCH v2 net-next 0/3] net: phy: aquantia: report Aquantia-specific settings and features

This series detects and reports quite some Aquantia-specific settings and features. v2: - propagate timeout in patch 2 Heiner Kallweit (3): net: phy: aquantia: print remote capabilities if link partner is Aquantia PHY net: phy: aquantia: report PHY details like firmware version net: phy

[PATCH v2 net-next 3/3] net: phy: aquantia: inform about proprietary 1000Base-T2 mode being in use

The AQCS109 supports a proprietary 2-pair 1Gbps mode. The standard registers don't allow to tell between 1000BaseT and 1000BaseT2. Add reporting this proprietary mode based on a vendor register. Signed-off-by: Heiner Kallweit Reviewed-by: Florian Fainelli --- drivers/net/phy/aquantia_main.c | 1

[PATCH v2 net-next 2/3] net: phy: aquantia: report PHY details like firmware version

Add reporting firmware details. These details are available only once the firmware has finished initializing the chip. This can take some time and we need to poll for init completion. v2: - Propagate timeout in aqr107_wait_reset_complete(). Don't bail out completely on timeout because chip may b

[PATCH v2 net-next 1/3] net: phy: aquantia: print remote capabilities if link partner is Aquantia PHY

If both link partners are Aquantia PHY's then additional information is exchanged as part of the auto-negotiation. Report remote capabilities if link partner is Aquantia PHY. Signed-off-by: Heiner Kallweit Reviewed-by: Florian Fainelli --- drivers/net/phy/aquantia_main.c | 49 ++

[patch net-next v3 00/15] devlink: small spring cleanup

From: Jiri Pirko Mostly cosmetics and janitor work. Jiri Pirko (15): net: devlink: add couple of missing mutex_destroy() calls bnxt: add missing net/devlink.h include dsa: add missing net/devlink.h include bnxt: set devlink port attrs properly bnxt: call devlink_port_type_eth_set() bef

[patch net-next v3 15/15] net: devlink: select NET_DEVLINK from drivers

From: Jiri Pirko Some drivers are becoming more dependent on NET_DEVLINK being selected in configuration. With upcoming compat functions, the behavior would be wrong in case devlink was not compiled in. So make the drivers select NET_DEVLINK and rely on the functions being there, not just stubs.

[patch net-next v3 14/15] net: devlink: add port type spinlock

From: Jiri Pirko Add spinlock to protect port type and type_dev pointer consistency. Without that, userspace may see inconsistent type and type_dev combinations. Signed-off-by: Jiri Pirko v1->v2: - rebased --- include/net/devlink.h | 4 net/core/devlink.c| 17 + 2 fil

[patch net-next v3 08/15] mlxsw: Move devlink_port_attrs_set() call before register

From: Jiri Pirko Since attrs are static during the existence of devlink port, set the before registration of the port. Signed-off-by: Jiri Pirko --- drivers/net/ethernet/mellanox/mlxsw/core.c | 12 ++-- drivers/net/ethernet/mellanox/mlxsw/core.h | 8 drivers/net/ether

[patch net-next v3 02/15] bnxt: add missing net/devlink.h include

From: Jiri Pirko devlink functions are in use, so include the related header file. Signed-off-by: Jiri Pirko --- drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c b/drivers/net/ethernet/broad

[patch net-next v3 13/15] net: devlink: warn on setting type on unregistered port

From: Jiri Pirko Port needs to be registered first before the type is set. Warn and bail-out in case it is not. Signed-off-by: Jiri Pirko --- v1->v2: - new patch --- net/core/devlink.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/net/core/devlink.c b/net/core/devlink.c index f4dbd4046

[patch net-next v3 12/15] bnxt: set devlink port type after registration

From: Jiri Pirko Move the type set of devlink port after it is registered. Signed-off-by: Jiri Pirko --- v1->v2: - new patch --- drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt_devlink

[patch net-next v3 11/15] nfp: move devlink port type set after netdev registration

From: Jiri Pirko Similar to other driver, move the port type set after netdev registration is done. Along with that, clear the type before unregistration. Signed-off-by: Jiri Pirko --- v2->v3: - move type set to be called before nfp_app_vnic_init() v1->v2: - new patch --- drivers/net/ethernet/

[patch net-next v3 03/15] dsa: add missing net/devlink.h include

From: Jiri Pirko devlink functions are in use, so include the related header file. Signed-off-by: Jiri Pirko Reviewed-by: Andrew Lunn --- net/dsa/dsa2.c | 1 + 1 file changed, 1 insertion(+) diff --git a/net/dsa/dsa2.c b/net/dsa/dsa2.c index c00ee464afc7..4558de672b4f 100644 --- a/net/dsa/ds

[patch net-next v3 10/15] net: devlink: disallow port_attrs_set() to be called before register

From: Jiri Pirko Since the port attributes are static and cannot change during the port lifetime, WARN_ON if some driver calls it after registration. Also, no need to call notifications as it is noop anyway due to check of devlink_port->registered there. Signed-off-by: Jiri Pirko --- net/core/

[patch net-next v3 07/15] net: devlink: don't pass return value of __devlink_port_type_set()

From: Jiri Pirko __devlink_port_type_set() returns void, it makes no sense to pass it on, so don't do that. Signed-off-by: Jiri Pirko --- net/core/devlink.c | 9 +++-- 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/net/core/devlink.c b/net/core/devlink.c index b40fd1addf14..

[patch net-next v3 01/15] net: devlink: add couple of missing mutex_destroy() calls

From: Jiri Pirko Add missing called to mutex_destroy() for two mutexes used in devlink code. Signed-off-by: Jiri Pirko --- net/core/devlink.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/net/core/devlink.c b/net/core/devlink.c index da0a29f30885..1fe772eb18af 100644 --- a/net/core/dev

[patch net-next v3 04/15] bnxt: set devlink port attrs properly

From: Jiri Pirko Set the attrs properly so delink has enough info to generate physical port names. Signed-off-by: Jiri Pirko --- drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c b/drivers/

[patch net-next v3 06/15] net: devlink: don't take devlink_mutex for devlink_compat_*

From: Jiri Pirko The netdevice is guaranteed to not disappear so we can rely that devlink_port and devlink won't disappear as well. No need to take devlink_mutex so don't take it here. Signed-off-by: Jiri Pirko --- net/core/devlink.c | 18 -- 1 file changed, 8 insertions(+), 10

[patch net-next v3 05/15] bnxt: call devlink_port_type_eth_set() before port register

From: Jiri Pirko Call devlink_port_type_eth_set() before devlink_port_register(). Bnxt instances won't change type during lifetime. This avoids one extra userspace devlink notification. Signed-off-by: Jiri Pirko --- drivers/net/ethernet/broadcom/bnxt/bnxt_devlink.c | 2 +- 1 file changed, 1 in

[patch net-next v3 09/15] dsa: move devlink_port_attrs_set() call before register

From: Jiri Pirko Since attrs are static during the existence of devlink port, set the before registration of the port. Signed-off-by: Jiri Pirko Reviewed-by: Andrew Lunn --- v1->v2: - fixed comment for port numbering --- net/dsa/dsa2.c | 47 ++- 1 f

Re: [PATCH net-next] net: use bulk free in kfree_skb_list

On Sun, 24 Mar 2019 07:58:34 +0100 Felix Fietkau wrote: > Since we're freeing multiple skbs, we might as well use bulk free to save a > few cycles. Use the same conditions for bulk free as in napi_consume_skb. > > Signed-off-by: Felix Fietkau Thanks for working on this, it's been on my todo li

[PATCH iproute2] tc: add dualpi2 scheduler module

DUALPI2 AQM is a combination of the DUALQ Coupled-AQM with a PI2 base-AQM, able to control scalable congestion controls like DCTCP and TCP-Prague. The PI2 AQM details can be found in the paper: CoNEXT '16 Proceedings of the 12th International on Conference on emerging Networking EXperiments and Tec

Re: [PATCH net-next] ipv6: Move ipv6 stubs to a separate header file

On 3/23/19 9:55 PM, Alexei Starovoitov wrote: > On Sat, Mar 23, 2019 at 09:40:23PM -0400, David Miller wrote: >> From: David Ahern >> Date: Fri, 22 Mar 2019 06:06:09 -0700 >> >>> From: David Ahern >>> >>> The number of stubs is growing and has nothing to do with addrconf. >>> Move the definition

Re: [BUG][iproute2][5.0] ip route show table default: "Error: ipv4: FIB table does not exist."

On 3/23/19 7:00 AM, emersonbern...@tutanota.com wrote: > After upgrading iproute2 from 4.20 to 5.0 the following error occurs: > > $ ip route show table default > Error: ipv4: FIB table does not exist. > Dump terminated > > The command works for all tables other than 'default' one. It seems relat

[PATCH net-next 0/2] ethtool: add support for Fast Link Down as new PHY tunable

This adds support for Fast Link Down as new PHY tunable. Fast Link Down reduces the time until a link down event is reported for 1000BaseT. According to the standard it's 750ms what is too long for several use cases. This is the kernel-related series, the ethtool userspace extension I'd submit onc

[PATCH net-next 1/2] ethtool: add PHY Fast Link Down support

This adds support for Fast Link Down as new PHY tunable. Fast Link Down reduces the time until a link down event is reported for 1000BaseT. According to the standard it's 750ms what is too long for several use cases. Signed-off-by: Heiner Kallweit --- include/uapi/linux/ethtool.h | 4 net/c

[PATCH net-next 2/2] net: phy: marvell: add PHY tunable fast link down support for 88E1540

1000BaseT standard requires that a link is reported as down earliest after 750ms. Several use case however require a much faster detecion of a broken link. Fast Link Down supports this by intentionally violating a the standard. This patch exposes the Fast Link Down feature of 88E1540 and 88E6390. T

Re: [PATCH bpf-next 0/7] bpf: Propagate cn to TCP

On Sat, Mar 23, 2019 at 10:36:24PM -0700, Eric Dumazet wrote: > > > On 03/23/2019 08:41 AM, Alexei Starovoitov wrote: > > On Sat, Mar 23, 2019 at 02:12:39AM -0700, Eric Dumazet wrote: > >> > >> > >> On 03/23/2019 01:05 AM, brakmo wrote: > >>> This patchset adds support for propagating congestion

Re: [PATCH net-next] net: use bulk free in kfree_skb_list

On 2019-03-24 12:31, Jesper Dangaard Brouer wrote: > On Sun, 24 Mar 2019 07:58:34 +0100 > Felix Fietkau wrote: > >> Since we're freeing multiple skbs, we might as well use bulk free to save a >> few cycles. Use the same conditions for bulk free as in napi_consume_skb. >> >> Signed-off-by: Felix

[PATCH v2] net: use bulk free in kfree_skb_list

Since we're freeing multiple skbs, we might as well use bulk free to save a few cycles. Use the same conditions for bulk free as in napi_consume_skb. Signed-off-by: Felix Fietkau --- v2: call kmem_cache_free_bulk once the skb array is full instead of falling back to kfree_skb net/core/skbuff

Re: [BUG][iproute2][5.0] ip route show table default: "Error: ipv4: FIB table does not exist."

Mar 24, 2019, 2:17 PM by dsah...@gmail.com: > On 3/23/19 7:00 AM, > emersonbern...@tutanota.com > > wrote: > >> After upgrading iproute2 from 4.20 to 5.0 the following error occurs: >> >> $ ip route show table default >> Error: ipv4: FIB table does not exist.

Re: [BUG][iproute2][5.0] ip route show table default: "Error: ipv4: FIB table does not exist."

On 3/24/19 11:02 AM, emersonbern...@tutanota.com wrote: > Ok but previous versions of iproute2 didn't treat this as error and didn't > exited with non-zero status. Is non existing default route a system error > which needs fixing? The kernel is returning that error, not iproute2. It is the defa

Re: [BUG][iproute2][5.0] ip route show table default: "Error: ipv4: FIB table does not exist."

Mar 24, 2019, 5:20 PM by dsah...@gmail.com: > On 3/24/19 11:02 AM, > emersonbern...@tutanota.com > > wrote: > >> Ok but previous versions of iproute2 didn't treat this as error and didn't >> exited with non-zero status. Is non existing default route a system

Re: [BUG][iproute2][5.0] ip route show table default: "Error: ipv4: FIB table does not exist."

On 3/24/19 11:34 AM, emersonbern...@tutanota.com wrote: > Mar 24, 2019, 5:20 PM by dsah...@gmail.com: > >> On 3/24/19 11:02 AM, > emersonbern...@tutanota.com >> > wrote: >> >>> Ok but previous versions of iproute2 didn't treat this as error and didn't >>> exi

Re: [PATCH v2] net: use bulk free in kfree_skb_list

On Sun, 24 Mar 2019 17:56:44 +0100 Felix Fietkau wrote: > Since we're freeing multiple skbs, we might as well use bulk free to save a > few cycles. Use the same conditions for bulk free as in napi_consume_skb. > > Signed-off-by: Felix Fietkau > --- > v2: call kmem_cache_free_bulk once the skb a

Re: [PATCH net] dpaa2-eth: Fix possible access beyond end of array

On Wed, 20 Mar 2019 14:11:04 + Ioana Ciocoi Radulescu wrote: > Make sure we don't try to enqueue XDP_REDIRECT frames to an > inexistent FQ. > > While it is guaranteed not to have more than one queue per core, > having fewer queues than CPUs on an interface is a valid > configuration. > > Fi

Re: [BUG][iproute2][5.0] ip route show table default: "Error: ipv4: FIB table does not exist."

On Sun, Mar 24, 2019 at 11:20:33AM -0600, David Ahern wrote: > On 3/24/19 11:02 AM, emersonbern...@tutanota.com wrote: > > Ok but previous versions of iproute2 didn't treat this as error and didn't > > exited with non-zero status. Is non existing default route a system error > > which needs fixin

Re: [BUG][iproute2][5.0] ip route show table default: "Error: ipv4: FIB table does not exist."

On Sun, Mar 24, 2019 at 07:29:08PM +0100, Michal Kubecek wrote: > On Sun, Mar 24, 2019 at 11:20:33AM -0600, David Ahern wrote: > > On 3/24/19 11:02 AM, emersonbern...@tutanota.com wrote: > > > Ok but previous versions of iproute2 didn't treat this as error and > > > didn't exited with non-zero sta

Re: [PATCH net-next] openvswitch: Make metadata_dst tunnel work in IP_TUNNEL_INFO_BRIDGE mode

On Sun, Mar 24, 2019 at 12:03 AM wenxu wrote: > > On 2019/3/24 上午5:39, Pravin Shelar wrote: > > On Sat, Mar 23, 2019 at 2:18 AM wenxu wrote: > >> On 2019/3/23 下午3:50, Pravin Shelar wrote: > >> > >> On Thu, Mar 21, 2019 at 3:34 AM wrote: > >> > >> From: wenxu > >> > >> There is currently no supp

[PATCH net-next] net: openvswitch: Add a new action check_pkt_len

From: Numan Siddique This patch adds a new action - 'check_pkt_len' which checks the packet length and executes a set of actions if the packet length is greater than the specified length or executes another set of actions if the packet length is lesser or equal to. This action takes below nlattr

[PATCH net-next] net-next: add dualpi2 scheduler module

DUALPI2 provides extremely low latency & loss to traffic that uses a scalable congestion controller (e.g. L4S, DCTCP) without degrading the performance of 'classic' traffic (e.g. Reno, Cubic etc.). It is intended to be the reference implementation of the IETF's DualQ Coupled AQM. The qdisc provide

Re: [RFC PATCH net-next 01/13] lib: Add support for generic packing operations

On Sun, Mar 24, 2019 at 05:23:34AM +0200, Vladimir Oltean wrote: > This provides an unified API for accessing register bit fields > regardless of memory layout. The basic unit of data for these API > functions is the u64. The process of transforming an u64 from native CPU > encoding into the periph

Re: [patch net-next v3 00/15] devlink: small spring cleanup

From: Jiri Pirko Date: Sun, 24 Mar 2019 11:14:23 +0100 > Mostly cosmetics and janitor work. Series applied, thanks Jiri.

Re: [RFC PATCH net-next 01/13] lib: Add support for generic packing operations

On 3/24/19 9:02 PM, Richard Cochran wrote: On Sun, Mar 24, 2019 at 05:23:34AM +0200, Vladimir Oltean wrote: This provides an unified API for accessing register bit fields regardless of memory layout. The basic unit of data for these API functions is the u64. The process of transforming an u64 fr

Re: [RFC PATCH net-next 02/13] net: dsa: Store vlan_filtering as a property of dsa_port

On Sun, Mar 24, 2019 at 05:23:35AM +0200, Vladimir Oltean wrote: > This allows drivers to query the VLAN setting imposed by the bridge > driver directly from DSA, instead of keeping their own state based on > the .port_vlan_filtering callback. Hi Vladimir It would be good to modify the mt7530 dri

Re: [PATCH net-next] fou: Support binding FoU socket

Hi, On Thu, Mar 21, 2019 at 9:10 PM David Miller wrote: > This seems to allow adding both a wildcarded and a non-wildcarded fou > socket, which otherwise has overlapping match scenerios. > > I don't think you want to allow that unless you can determine that > you aren't creating a situation where

[PATCHv2 net-next] sched: add dualpi2 scheduler module

DUALPI2 provides extremely low latency & loss to traffic that uses a scalable congestion controller (e.g. L4S, DCTCP) without degrading the performance of 'classic' traffic (e.g. Reno, Cubic etc.). It is intended to be the reference implementation of the IETF's DualQ Coupled AQM. The qdisc provide

Re: [BUG][iproute2][5.0] ip route show table default: "Error: ipv4: FIB table does not exist."

On 3/24/19 12:36 PM, Michal Kubecek wrote: > On Sun, Mar 24, 2019 at 07:29:08PM +0100, Michal Kubecek wrote: >> On Sun, Mar 24, 2019 at 11:20:33AM -0600, David Ahern wrote: >>> On 3/24/19 11:02 AM, emersonbern...@tutanota.com wrote: Ok but previous versions of iproute2 didn't treat this as err

Re: [PATCH bpf-next v2] bpf: silence uninitialized var warning in bpf_skb_net_grow

On Sat, Mar 23, 2019 at 9:23 AM Willem de Bruijn wrote: > > From: Willem de Bruijn > > These three variables are set in one branch and used in another with > the same condition. But on some architectures they still generate > compiler warnings of the kind: > > warning: 'inner_trans' may be used

Re: [ovs-dev] [PATCH net-next] openvswitch: Make metadata_dst tunnel work in IP_TUNNEL_INFO_BRIDGE mode

On Sat, Mar 23, 2019 at 5:28 PM wenxu wrote: > > On 2019/3/23 下午3:50, Pravin Shelar wrote: > > On Thu, Mar 21, 2019 at 3:34 AM wrote: > >> From: wenxu > >> > >> There is currently no support for the multicasti/broadcst aspects > >> of VXLAN in ovs. In the datapath flow the tun_dst must specific.

Re: [PATCH net-next] openvswitch: Make metadata_dst tunnel work in IP_TUNNEL_INFO_BRIDGE mode

On 2019/3/25 上午2:46, Pravin Shelar wrote: > On Sun, Mar 24, 2019 at 12:03 AM wenxu wrote: >> On 2019/3/24 上午5:39, Pravin Shelar wrote: >>> On Sat, Mar 23, 2019 at 2:18 AM wenxu wrote: On 2019/3/23 下午3:50, Pravin Shelar wrote: On Thu, Mar 21, 2019 at 3:34 AM wrote: From:

Re: [PATCH net-next] net-next: add dualpi2 scheduler module

Hi Olga, Thank you for the patch! Yet something to improve: [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Olga-Albisser/net-next-add-dualpi2-scheduler-module/20190325-083045 config: ia64-allmodconfig (attached as .config) compiler: ia64-linux-gcc (G

Re: [ovs-dev] [PATCH net-next] openvswitch: Make metadata_dst tunnel work in IP_TUNNEL_INFO_BRIDGE mode

On Mon, Mar 25, 2019 at 9:24 AM wenxu wrote: > > On 2019/3/25 上午2:46, Pravin Shelar wrote: > > On Sun, Mar 24, 2019 at 12:03 AM wenxu wrote: > >> On 2019/3/24 上午5:39, Pravin Shelar wrote: > >>> On Sat, Mar 23, 2019 at 2:18 AM wenxu wrote: > On 2019/3/23 下午3:50, Pravin Shelar wrote: > >

Re: [PATCH bpf v2 0/2] libbpf fix up and clarify version info

On Fri, Mar 22, 2019 at 5:49 PM Daniel Borkmann wrote: > > First one is fixing version in Makefile and shared object and > second one clarifies bump in version. Thanks! > > v1 -> v2: > - Fix up soname, thanks Stanislav! Applied. Thanks!

pull-request: bpf 2019-03-24

Hi David, The following pull-request contains BPF updates for your *net* tree. The main changes are: 1) libbpf verision fix up from Daniel. 2) fix liveness propagation from Jakub. 3) fix verbose print of refcounted regs from Martin. 4) fix for large map allocations from Martynas. 5) fix use

Re: [ovs-dev] [PATCH net-next] openvswitch: Make metadata_dst tunnel work in IP_TUNNEL_INFO_BRIDGE mode

On 3/25/2019 9:47 AM, Tonghao Zhang wrote: > On Mon, Mar 25, 2019 at 9:24 AM wenxu wrote: >> On 2019/3/25 上午2:46, Pravin Shelar wrote: >>> On Sun, Mar 24, 2019 at 12:03 AM wenxu wrote: On 2019/3/24 上午5:39, Pravin Shelar wrote: > On Sat, Mar 23, 2019 at 2:18 AM wenxu wrote: >> On 2

Re: [PATCH net-next] ipv6: Move ipv6 stubs to a separate header file

On Sun, Mar 24, 2019 at 06:56:42AM -0600, David Ahern wrote: > > This change also enables many other key features: > 1. IPv4 multipath routes are not evicted just because 1 hop goes down. > 2. IPv6 multipath routes with device only nexthops (e.g., tunnels). > 3. IPv6 nexthop with IPv4 route (aka,

Re: pull-request: bpf 2019-03-24

From: Alexei Starovoitov Date: Sun, 24 Mar 2019 19:57:55 -0700 > The main changes are: > > 1) libbpf verision fix up from Daniel. > > 2) fix liveness propagation from Jakub. > > 3) fix verbose print of refcounted regs from Martin. > > 4) fix for large map allocations from Martynas. > > 5) fi

Re: [PATCHv2 net-next] sched: add dualpi2 scheduler module

Hi Olga, Thank you for the patch! Yet something to improve: [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Olga-Albisser/sched-add-dualpi2-scheduler-module/20190325-113536 config: x86_64-allmodconfig (attached as .config) compiler: gcc-7 (Debian 7.3.

Re: [PATCHv2 net-next] sched: add dualpi2 scheduler module

Sun, Mar 24, 2019 at 10:52:53PM CET, olga...@gmail.com wrote: >DUALPI2 provides extremely low latency & loss to traffic that uses a >scalable congestion controller (e.g. L4S, DCTCP) without degrading the >performance of 'classic' traffic (e.g. Reno, Cubic etc.). It is intended >to be the reference

Re: [PATCH v9 3/6] anybus-s: support the Arcx anybus controller

Hi Sven, Thank you for the patch! Yet something to improve: [auto build test ERROR on staging/staging-testing] [also build test ERROR on v5.1-rc2 next-20190325] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci