[PATCH v2 net-next v2 11/12] net: dsa: mv88e6xxx: add G1 helper for ageing time

All Marvell switch chips from (88E6060 to 88E6390) have a ATU Control register containing bits 11:4 to configure an ATU Age Time quotient. However the coefficient used to calculate the ATU Age Time vary with the models. E.g. 88E6060, 88E6352 and 88E6390 use respectively 16, 15 and 3.75 seconds.

[PATCH v2 net-next v2 10/12] net: dsa: support switchdev ageing time attr

Add a new function for DSA drivers to implement to handle the switchdev SWITCHDEV_ATTR_ID_BRIDGE_AGEING_TIME attribute. The ageing time is passed as milliseconds. Signed-off-by: Vivien Didelot --- include/net/dsa.h | 1 + net/dsa/slave.c | 22

[PATCH v2 net-next v2 04/12] net: dsa: mv88e6xxx: extract trunk mapping

The Trunk Mask and Trunk Mapping registers are two Global 2 indirect accesses to trunking configuration. Add helpers for these tables and simplify the Global 2 setup. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx/chip.c | 70

[PATCH v2 net-next v2 05/12] net: dsa: mv88e6xxx: add cap for MGMT Enables bits

Some switches provide a Rsvd2CPU mechanism used to choose which of the 16 reserved multicast destination addresses matching 01:80:c2:00:00:0x should be considered as MGMT and thus forwarded to the CPU port. Other switches extend this mechanism to also configure as MGMT the additional 16 reserved

[PATCH v2 net-next v2 07/12] net: dsa: mv88e6xxx: add cap for PVT

Add flags to describe the presence of Cross-chip Port VLAN Table (PVT) related registers and simplify the setup of Global 2. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx/chip.c | 16 drivers/net/dsa/mv88e6xxx/mv88e6xxx.h

[PATCH v2 net-next v2 01/12] net: dsa: mv88e6xxx: remove basic function flags

All 88E6xxx Marvell switches (even the old not supported yet 88E6060) have at least an ATU, per-port STP states and VLAN map, to run basic switch functions such as Spanning Tree and port based VLANs. Get rid of the related MV88E6XXX_FLAG_{ATU,PORTSTATE,VLANTABLE} flags, as they are defaults to

[PATCH v2 net-next v2 12/12] net: dsa: mv88e6xxx: add support for DSA ageing time

Implement the DSA driver function to configure the bridge ageing time. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx/chip.c | 14 ++ 1 file changed, 14 insertions(+) diff --git a/drivers/net/dsa/mv88e6xxx/chip.c

[PATCH v2 net-next v2 09/12] net: dsa: mv88e6xxx: add cap for IRL

Add capability flags to describe the presence of Ingress Rate Limit unit registers and an helper function to clear it. In the meantime, fix a few harmless issues: - 6185 and 6095 don't have such registers (reserved) - the previous code didn't wait for the IRL operation to complete

[PATCH v2 net-next v2 03/12] net: dsa: mv88e6xxx: extract device mapping

The Device Mapping register is an indirect table access. Provide helpers to access this table and explicit the checking of the new DSA_RTABLE_NONE routing table value. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx/chip.c | 76

RE: [RFC PATCH 00/30] Kernel NET policy

> > Hi Kan, > > On 07/18/2016 08:55 AM, kan.li...@intel.com wrote: > > From: Kan Liang > > > > It is a big challenge to get good network performance. First, the > > network performance is not good with default system settings. Second, > > it is too difficult to do

Re: [PATCH] net/sched/sch_htb: clamp xstats tokens to fit into 32-bit int

On Sat, Jul 16, 2016 at 7:08 AM, Konstantin Khlebnikov wrote: > In kernel HTB keeps tokens in signed 64-bit in nanoseconds. In netlink > protocol these values are converted into pshed ticks (64ns for now) and > truncated to 32-bit. In struct tc_htb_xstats fields

RE: [PATCH] wlcore/wl18xx: mesh: added initial mesh support for wl8

On Mon, Jul 18, 2016 at 20:42:57, Kalle Valo wrote: > Guy; Johannes Berg; Arik Nemtsov; linux-wirel...@vger.kernel.org; > netdev@vger.kernel.org > Subject: Re: [PATCH] wlcore/wl18xx: mesh: added initial mesh support > for wl8 > > Yaniv Machani writes: > > > From: Maital Hahn

RE: [RFC PATCH 00/30] Kernel NET policy

> On Mon, Jul 18, 2016 at 5:51 PM, Liang, Kan wrote: > > > > > >> > > >> > It is a big challenge to get good network performance. First, the > >> > network performance is not good with default system settings. > >> > Second, it is too difficult to do automatic tuning for

Re: [RFC PATCH 00/30] Kernel NET policy

On Mon, Jul 18, 2016 at 8:45 AM, Andi Kleen wrote: >> It seems strange to me to add such policies to the kernel. >> Addmittingly, documentation of some settings is non-existent and one needs >> various different tools to set this (sysctl, procfs, sysfs, ethtool, etc). > > The

Re: [PATCH 1/1] Update maintainer for EHEA driver.

On Mon, Jul 18, 2016 at 12:28:45PM -0500, Douglas Miller wrote: > Since Thadeu left IBM, EHEA has gone mostly unmaintained, since his email > address doesn't work anymore. I'm stepping up to help maintain this > driver upstream. > > I'm adding Thadeu's personal e-mail address in Cc, hoping that

Re: [PATCH] wlcore/wl18xx: mesh: added initial mesh support for wl8

Yaniv Machani writes: > From: Maital Hahn > > 1. Added support for interface and role of mesh type. > 2. Enabled enable/start of mesh-point role, >and opening and closing a connection with a mesh peer. > 3. Added multirole combination of mesh and ap >

RE: [RFC PATCH 00/30] Kernel NET policy

> > > > It seems strange to me to add such policies to the kernel. > > > > But kernel is the only place which can merge all user's requests. > > I don't think so. > > If different requests conflict in a way that is possible to dosomething > meaningful the I don't see why userspace tool cannot

Re: [PATCH net-next 1/1] net_sched: Introduce skbmod action

On Mon, Jul 18, 2016 at 3:26 AM, Jamal Hadi Salim wrote: > On 16-07-18 06:07 AM, Thomas Graf wrote: > >> >> Right. I was at the same point as Jamal and it is nasty to try and >> reverse engineer the dumps without any further hints. I assume that's >> what he is referring to

[PATCH 1/1] Update maintainer for EHEA driver.

Since Thadeu left IBM, EHEA has gone mostly unmaintained, since his email address doesn't work anymore. I'm stepping up to help maintain this driver upstream. I'm adding Thadeu's personal e-mail address in Cc, hoping that we can get his ack. CC: Thadeu Lima de Souza Cascardo

Re: [PATCH v9 00/11] Add driver bpf hook for early packet drop and forwarding

On Mon, Jul 18, 2016 at 09:38:28AM -0700, Brenden Blanco wrote: > On Mon, Jul 18, 2016 at 04:39:38PM +0300, Tariq Toukan wrote: > > After applying the patchset, I get no ping between two VLAN > > interfaces (w/o activating any BPF program). > > I'm debugging it, and will update once I find the

Re: [PATCH v5] wlcore: spi: add wl18xx support

"Reizer, Eyal" writes: > Add support for using with both wl12xx and wl18xx. > > - all wilink family needs special init command for entering wspi mode. > extra clock cycles should be sent after the spi init command while the > cs pin is high. > - Use inverted chip select for

Re: [RFC PATCH 30/30] Documentation/networking: Document net policy

On 07/17/16 23:56, kan.li...@intel.com wrote: > From: Kan Liang > > Signed-off-by: Kan Liang > --- > Documentation/networking/netpolicy.txt | 158 > + > 1 file changed, 158 insertions(+) > create mode 100644

Re: [RFC PATCH 00/30] Kernel NET policy

On Sun, Jul 17, 2016 at 11:55 PM, wrote: > From: Kan Liang > > It is a big challenge to get good network performance. First, the network > performance is not good with default system settings. Second, it is too > difficult to do automatic tuning for all

Re: [PATCH v9 00/11] Add driver bpf hook for early packet drop and forwarding

On Mon, Jul 18, 2016 at 04:39:38PM +0300, Tariq Toukan wrote: > After applying the patchset, I get no ping between two VLAN > interfaces (w/o activating any BPF program). > I'm debugging it, and will update once I find the bug. > > Brenden, please check if you can repro the issue. I was able to

Re: [RFC PATCH 00/30] Kernel NET policy

On Mon, Jul 18, 2016 at 5:51 PM, Liang, Kan wrote: > > >> > >> > It is a big challenge to get good network performance. First, the >> > network performance is not good with default system settings. Second, >> > it is too difficult to do automatic tuning for all possible

Re: [RFC PATCH 00/30] Kernel NET policy

Hi Kan, On 07/18/2016 08:55 AM, kan.li...@intel.com wrote: From: Kan Liang It is a big challenge to get good network performance. First, the network performance is not good with default system settings. Second, it is too difficult to do automatic tuning for all possible

Re: [RFC PATCH 23/30] i40e/ethtool: support RX_CLS_LOC_ANY

On Sun, Jul 17, 2016 at 11:56 PM, wrote: > From: Kan Liang > > The existing special location RX_CLS_LOC_ANY flag is designed for the > case which the caller does not know/care about the location. Now, this > flag is only handled in ethtool user space.

Re: [iproute PATCH v5 2/5] Use C99 style initializers everywhere

On 7/18/16 8:48 AM, Phil Sutter wrote: This big patch was compiled by vimgrepping for memset calls and changing to C99 initializer if applicable. One notable exception is the initialization of union bpf_attr in tc/tc_bpf.c: changing it would break for older gcc versions (at least <=3.4.6).

Re: [iproute PATCH v5 3/5] Replace malloc && memset by calloc

On 7/18/16 8:48 AM, Phil Sutter wrote: This only replaces occurrences where the newly allocated memory is cleared completely afterwards, as in other cases it is a theoretical performance hit although code would be cleaner this way. Signed-off-by: Phil Sutter --- Changes since v2:

Re: [iproute PATCH v5 1/5] tc: m_action: Improve conversion to C99 style initializers

On 7/18/16 8:48 AM, Phil Sutter wrote: This improves my initial change in the following points: - Flatten embedded struct's initializers. - No need to initialize variables to zero as the key feature of C99 initializers is to do this implicitly. - By relocating the declaration of struct rtattr

Re: [RFC PATCH 00/30] Kernel NET policy

Liang, Kan wrote: > > What is missing in the kernel UAPI so userspace could do these settings on > > its > > own, without adding this policy stuff to the kernel? > > The main purpose of the proposal is to simplify the configuration. Too many > options will let them confuse.

Re: [iproute PATCH v5 4/5] No need to initialize rtattr fields before parsing

On 7/18/16 8:48 AM, Phil Sutter wrote: Since parse_rtattr_flags() calls memset already, there is no need for callers to do so themselves. Signed-off-by: Phil Sutter --- ip/ipaddress.c | 2 +- tc/tc_class.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) Acked-by:

Re: [iproute PATCH v5 5/5] Makefile: Allow to override CC

On 7/18/16 8:48 AM, Phil Sutter wrote: This makes it easier to build iproute2 with a custom compiler. While at it, make HOSTCC default to the value of CC if not explicitly set elsewhere. Signed-off-by: Phil Sutter --- Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2

RE: [RFC PATCH 00/30] Kernel NET policy

> > > > It is a big challenge to get good network performance. First, the > > network performance is not good with default system settings. Second, > > it is too difficult to do automatic tuning for all possible workloads, > > since workloads have different requirements. Some workloads may want

Re: [RFC PATCH 00/30] Kernel NET policy

> It seems strange to me to add such policies to the kernel. > Addmittingly, documentation of some settings is non-existent and one needs > various different tools to set this (sysctl, procfs, sysfs, ethtool, etc). The problem is that different applications need different policies. The only

Re: [PATCH 3/4] Marvell phy: add configuration of autonegociation for fiber link.

On Mon, Jul 18, 2016 at 11:03:42AM +0200, Charles-Antoine Couret wrote: Hi Charles-Antoine You really should have some sort of comment here which will go into the commit log. It can just be the Subject said differently. Reviewed-by: Andrew Lunn Andrew

Re: [PATCH 2/4] Marvell phy: add field to get errors from fiber link.

On Mon, Jul 18, 2016 at 11:03:41AM +0200, Charles-Antoine Couret wrote: > Add support for the fiber receiver error counter in the > statistics. Rename the current counter which is for copper errors to > phy_receive_errors_copper, so it is easy to distinguish copper from > fiber. > >

Re: [PATCH 4/4] Marvell phy: add functions to suspend and resume both interfaces: fiber and copper links.

On Mon, Jul 18, 2016 at 11:03:43AM +0200, Charles-Antoine Couret wrote: Again, a commit message is needed. Reviewed-by: Andrew Lunn Andrew

[PATCH net 0/2] Safe flow for mlx4_en configuration change

Hi Dave, This patchset improves the mlx4_en driver resiliency, especially on systems with low memory. Upon a configuration change that requires the allocation of new resources, we first try to allocate, prior to destroying the current ones. Once it is successfully done, we release the old

[PATCH net 1/2] net/mlx4_en: Move filters cleanup to a proper location

From: Eugenia Emantayev Filters cleanup should be done once before destroying net device, since filters list is contained in the private data. Fixes: 1eb8c695bda9 ('net/mlx4_en: Add accelerated RFS support') Signed-off-by: Eugenia Emantayev

[PATCH net 2/2] net/mlx4_en: Add resilience in low memory systems

From: Eugenia Emantayev This patch fixes the lost of Ethernet port on low memory system, when driver frees its resources and fails to allocate new resources. Issue could happen while changing number of channels, rings size or changing the timestamp configuration. This fix

Re: [PATCH 1/4] Marvell phy: check link status in case of fiber link.

On Mon, Jul 18, 2016 at 11:03:40AM +0200, Charles-Antoine Couret wrote: Hi Charles-Antoine Looking good. Just one nitpick. > /* marvell_read_status You missed changing this name above. > * > - * Generic status code does not detect Fiber correctly! > * Description: > * Check the link,

Re: [RFC PATCH 00/30] Kernel NET policy

kan.li...@intel.com wrote: > From: Kan Liang > > It is a big challenge to get good network performance. First, the network > performance is not good with default system settings. Second, it is too > difficult to do automatic tuning for all possible

[PATCH] virtio-vsock: Add timer to handle OOM situations

From: Gerard Garcia This patch applies over the stefanha/vsock-next repository: https://github.com/stefanha/linux/tree/vsock-next Once the guest puts a packet in the virtqueue it is guaranteed that it will be delivered. This patch addresses the problem of packets being

[PATCH] Add timer to handle OOM situations

From: Gerard Garcia Better testing support files Signed-off-by: Gerard Garcia --- drivers/vhost/vsock.c | 52 ++- 1 file changed, 47 insertions(+), 5 deletions(-) diff --git a/drivers/vhost/vsock.c

Re: [PATCH net-next] cdc_ether: Improve ZTE MF823/831/910 handling

On Mon, Jul 18, 2016 at 4:14 PM, Oliver Neukum wrote: >> Ok, sounds good. So far, I have only seen the random MAC issue with >> the three previously mentioned devices, but who knows how many else is >> out there with the same error ... I don't think it should be in the >> core

[iproute PATCH v5 4/5] No need to initialize rtattr fields before parsing

Since parse_rtattr_flags() calls memset already, there is no need for callers to do so themselves. Signed-off-by: Phil Sutter --- ip/ipaddress.c | 2 +- tc/tc_class.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/ip/ipaddress.c b/ip/ipaddress.c index

[iproute PATCH v5 5/5] Makefile: Allow to override CC

This makes it easier to build iproute2 with a custom compiler. While at it, make HOSTCC default to the value of CC if not explicitly set elsewhere. Signed-off-by: Phil Sutter --- Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile

[iproute PATCH v5 2/5] Use C99 style initializers everywhere

This big patch was compiled by vimgrepping for memset calls and changing to C99 initializer if applicable. One notable exception is the initialization of union bpf_attr in tc/tc_bpf.c: changing it would break for older gcc versions (at least <=3.4.6). Calls to memset for struct rtattr pointer

[iproute PATCH v5 3/5] Replace malloc && memset by calloc

This only replaces occurrences where the newly allocated memory is cleared completely afterwards, as in other cases it is a theoretical performance hit although code would be cleaner this way. Signed-off-by: Phil Sutter --- Changes since v2: - Fix checkpatch errors. --- genl/genl.c

[iproute PATCH v5 0/5] Big C99 style initializer rework

This is v5 of my C99-style initializer related patch series. The changes since v4 are: - Rebased to current origin/master with just a minor context conflict in patch 2. For reference, here's the v4 changelog: - Use empty initializer instead of the universal zero initializer: The latter one

[iproute PATCH v5 1/5] tc: m_action: Improve conversion to C99 style initializers

This improves my initial change in the following points: - Flatten embedded struct's initializers. - No need to initialize variables to zero as the key feature of C99 initializers is to do this implicitly. - By relocating the declaration of struct rtattr *tail, it can be initialized at the

[RFC PATCH 01/30] net: introduce NET policy

From: Kan Liang This patch introduce NET policy subsystem. If proc is supported in the system, it creates netpolicy node in proc system. Signed-off-by: Kan Liang --- include/linux/netdevice.h | 7 +++ include/net/net_namespace.h | 3 ++

[RFC PATCH 05/30] i40e/netpolicy: implement ndo_get_irq_info

From: Kan Liang Implement ndo_get_irq_info in i40e driver to get irq information of rx and tx queues. Signed-off-by: Kan Liang --- drivers/net/ethernet/intel/i40e/i40e_main.c | 40 + 1 file changed, 40 insertions(+) diff

[RFC PATCH 02/30] net/netpolicy: init NET policy

From: Kan Liang This patch tries to initialize NET policy for all the devices in the system. However, not all device drivers have NET policy support. For those drivers who does not have NET policy support, the node will not be showed in /proc/net/netpolicy/. The device

[RFC PATCH 09/30] net/netpolicy: enable and disable net policy

From: Kan Liang This patch introduces functions to enable and disable net policy. For enabling, it collects device and cpu information, setup cpu/queue mapping, and set irq affinity accordingly. For disabling, it removes the irq affinity and mapping information. np_lock

[RFC PATCH 08/30] net/netpolicy: set and remove irq affinity

From: Kan Liang This patches introduces functions to set and remove irq affinity according to cpu and queue mapping. The functions will not record the previous affinity status. After a set/remove cycles, it will set the affinity on all online cpu with irq balance enabling.

[RFC PATCH 07/30] net/netpolicy: create CPU and queue mapping

From: Kan Liang Current implementation forces CPU and queue 1:1 mapping. This patch introduces the function netpolicy_update_sys_map to create this mapping. The result is stored in netpolicy_sys_info. If the CPU count and queue count are different, the remaining CPUs/queues

[RFC PATCH 06/30] net/netpolicy: get CPU information

From: Kan Liang Net policy also needs to know CPU information. Currently, online CPU number is enough. Signed-off-by: Kan Liang --- net/core/netpolicy.c | 5 + 1 file changed, 5 insertions(+) diff --git a/net/core/netpolicy.c

[RFC PATCH 03/30] i40e/netpolicy: Implement ndo_netpolicy_init

From: Kan Liang Support ndo_netpolicy_init in i40e driver. For i40e driver, there is no extra initialization work to do. It only needs to update the available policy bitmap. policy_param will be filled according to different policies later. Signed-off-by: Kan Liang

[RFC PATCH 16/30] net/netpolicy: net device hotplug

From: Kan Liang Support net device up/down/namechange in the netpolicy code. Signed-off-by: Kan Liang --- net/core/netpolicy.c | 66 +--- 1 file changed, 58 insertions(+), 8 deletions(-) diff --git

[RFC PATCH 04/30] net/netpolicy: get driver information

From: Kan Liang Net policy needs to know device information. Currently, it's enough to only get irq information of rx and tx queues. This patch introduces ndo_get_irq_info to do so. Signed-off-by: Kan Liang --- include/linux/netdevice.h | 5 +

[RFC PATCH 13/30] i40e/netpolicy: add three new net policies

From: Kan Liang Introduce three net policies for i40e driver. CPU policy: configure for higher throughput and lower CPU%. BULK policy: configure for highest throughput. LATENCY policy: configure for lowest latency. Lots of tests are done for net policy on platforms with

[RFC PATCH 00/30] Kernel NET policy

From: Kan Liang It is a big challenge to get good network performance. First, the network performance is not good with default system settings. Second, it is too difficult to do automatic tuning for all possible workloads, since workloads have different requirements. Some

[RFC PATCH 11/30] net/netpolicy: set net policy by policy name

From: Kan Liang User can write policy name to /proc/net/netpolicy/$DEV/policy to enable net policy for specific device. When the policy is enabled, the module automatically disables irq balance and set irq affinity. The object list is also generated accordingly. np_lock

[RFC PATCH 17/30] net/netpolicy: support CPU hotplug

From: Kan Liang For CPU hotplug, the net policy module will rebuild the sys map and object list. Signed-off-by: Kan Liang --- net/core/netpolicy.c | 78 1 file changed, 78 insertions(+) diff --git

[RFC PATCH 15/30] i40e/netpolicy: add MIX policy support

From: Kan Liang Enable i40e MIX policy support. Based on the test, the MIX policy has better performance if increasing rx interrupt moderation a little bit. For evaluating the MIX policy performance, mixed workloads are tested. The mixed workloads are combination of

[RFC PATCH 18/30] net/netpolicy: handle channel changes

From: Kan Liang User can uses ethtool to set the channel number. This patch handles the channel changes by rebuilding the object list. Signed-off-by: Kan Liang --- include/linux/netpolicy.h | 8 net/core/ethtool.c| 8 +++-

[RFC PATCH 22/30] net/netpolicy: set tx queues according to policy

From: Kan Liang When the device tries to transmit a buffer, netdev_pick_tx is called to find the available tx queues. This patch checks the per socket net policy of the binding socket of the buffer. If net policy is set, it picks up the assigned tx queue from net policy

[RFC PATCH 26/30] net/netpolicy: set per task policy by proc

From: Kan Liang Users may not want to change the source code to add per task net polic support. Or they may want to change a running task's net policy. prctl does not work for both cases. This patch adds an interface in /proc, which can be used to set and retrieve policy of

[RFC PATCH 14/30] net/netpolicy: add MIX policy

From: Kan Liang MIX policy is combine of other policies. It allows different queue has different policy. If MIX policy is applied, /proc/net/netpolicy/$DEV/policy shows per queue policy. Usually, the workloads requires either high throughput or low latency. So for current

Re: [PATCH net-next] cdc_ether: Improve ZTE MF823/831/910 handling

On Mon, Jul 18, 2016 at 4:14 PM, Oliver Neukum wrote: >> Ok, sounds good. So far, I have only seen the random MAC issue with >> the three previously mentioned devices, but who knows how many else is >> out there with the same error ... I don't think it should be in the >> core

[RFC PATCH 10/30] net/netpolicy: introduce netpolicy object

From: Kan Liang This patch introduces the concept of netpolicy object and policy object list. The netpolicy object is the instance of CPU/queue mapping. The object can be shared between different tasks/sockets. So besides CPU and queue information, the object also maintains

[RFC PATCH 24/30] net/netpolicy: set rx queues according to policy

From: Kan Liang For setting rx queues, this patch add rules for Flow Director filters. Since we may not get all the information required for rule until the first package arrived, it will add the rule after recvmsg. The first several packages may not use the assigned queue.

[RFC PATCH 21/30] net/policy: introduce netpolicy_pick_queue

From: Kan Liang This function will be used to get assigned queues by policy and ptr. If it's first time, get_avail_queue will be called to find the available object from the given policy object list. Signed-off-by: Kan Liang ---

[RFC PATCH 20/30] net/netpolicy: introduce per socket netpolicy

From: Kan Liang The network socket is the most basic unit which control the network traffic. This patch introduces a new socket option SO_NETPOLICY to set/get net policy for socket. so that the application can set its own policy on socket to improve the network performance.

[RFC PATCH 19/30] net/netpolicy: implement netpolicy register

From: Kan Liang User can register itself in netpolicy module with specific policy. If it's the first time to register, an record will be created and inserted into RCU hash table. The record includes ptr, policy and object information. ptr is assigned by the user which is

[RFC PATCH 23/30] i40e/ethtool: support RX_CLS_LOC_ANY

From: Kan Liang The existing special location RX_CLS_LOC_ANY flag is designed for the case which the caller does not know/care about the location. Now, this flag is only handled in ethtool user space. If the kernel directly calls the ETHTOOL_SRXCLSRLINS interface with

[RFC PATCH 25/30] net/netpolicy: introduce per task net policy

From: Kan Liang Usually, application as a whole has specific requirement. Applying the net policy to all sockets one by one in the application is too complex. This patch introduces per task net policy to address this case. Once the per task net policy is applied, all the

[RFC PATCH 28/30] net/netpolicy: optimize for queue pair

From: Kan Liang Some drivers like i40e driver does not support separate tx and rx queues as channels. Using rx queue to stand for the channels, if queue_pair is set by driver. Signed-off-by: Kan Liang --- drivers/net/ethernet/intel/i40e/i40e_main.c |

[RFC PATCH 27/30] net/netpolicy: fast path for finding the queues

From: Kan Liang Current implementation searches the hash table to get assigned object for each transmit/receive packet. It's not necessory, because the assigned object usually remain unchanged. This patch store the assigned queue into netpolicy_reg struct. So it doesnot

[RFC PATCH 30/30] Documentation/networking: Document net policy

From: Kan Liang Signed-off-by: Kan Liang --- Documentation/networking/netpolicy.txt | 158 + 1 file changed, 158 insertions(+) create mode 100644 Documentation/networking/netpolicy.txt diff --git

[RFC PATCH 29/30] net/netpolicy: limit the total record number

From: Kan Liang NET policy can not fulfill users request without limit, because of the security consideration and device limitation. For security consideration, the attacker may fake millions of per task/socket request to crash the system. For device limitation, the flow

[RFC PATCH 12/30] i40e/netpolicy: implement ndo_set_net_policy

From: Kan Liang Setting net policy for all tx and rx queues according to policy name. For i40e driver, the policy only changes per queue interrupt moderation. It uses new ethtool callback (per queue coalesce setting) to configure the driver. Signed-off-by: Kan Liang

Re: [PATCH net-next] cdc_ether: Improve ZTE MF823/831/910 handling

On Mon, 2016-07-18 at 16:10 +0200, Kristian Evensen wrote: > On Mon, Jul 18, 2016 at 3:50 PM, Oliver Neukum wrote: > > No, you misunderstand me. I don't want quirks if we can avoid it. > > But if you need to do this for rndis_host and cdc_ether and maybe other > > drivers you

Re: [PATCH 0/2] Fix DMA channel misreporting for the Renesas Ethernet drivers

Hello. On 07/18/2016 09:24 AM, David Miller wrote: Here's a set of 2 patches against DaveM's 'net.git' repo fixing up the DMA channel reporting by 'ifconfig'... Is some fixing some ifconfig output that is effectively meaningless appropriate for 'net'? I just don't know any more users

Re: [PATCH net-next] cdc_ether: Improve ZTE MF823/831/910 handling

On Mon, Jul 18, 2016 at 3:50 PM, Oliver Neukum wrote: > No, you misunderstand me. I don't want quirks if we can avoid it. > But if you need to do this for rndis_host and cdc_ether and maybe other > drivers you should not be touching drivers. This belongs into the core > ethernet

[PATCH 1/1] ixgbevf: avoid checking hang when performing hardware reset

From: Zhu Yanjun When performing hardware reset, it is not necessary to check hang. Or else, the call trace will appear. Signed-off-by: Zhu Yanjun --- drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 5 + 1 file changed, 5 insertions(+) diff

Re: [PATCH net-next] cdc_ether: Improve ZTE MF823/831/910 handling

On Mon, 2016-07-18 at 15:23 +0200, Kristian Evensen wrote: > Hi, > > On Mon, Jul 18, 2016 at 3:01 PM, Oliver Neukum wrote: > > On Mon, 2016-07-18 at 14:24 +0200, Kristian Evensen wrote: > >> The firmware in the ZTE MF823/831/910 modems/mifis use OS fingerprinting to > >>

Re: [PATCH v9 00/11] Add driver bpf hook for early packet drop and forwarding

After applying the patchset, I get no ping between two VLAN interfaces (w/o activating any BPF program). I'm debugging it, and will update once I find the bug. Brenden, please check if you can repro the issue. Regards, Tariq

Re: [PATCH 3/3] mac80211: mesh: fixed HT ies in beacon template

On Wed, Jul 13, 2016 at 02:45:40PM +0300, Yaniv Machani wrote: > The HT capab info field inside the HT capab IE of the mesh beacon > is incorrect (in the case of 20MHz channel width). > To fix this driver will check configuration from cfg and > will build it accordingly. > +/* determine

Re: [PATCH net-next] cdc_ether: Improve ZTE MF823/831/910 handling

Hi, On Mon, Jul 18, 2016 at 3:01 PM, Oliver Neukum wrote: > On Mon, 2016-07-18 at 14:24 +0200, Kristian Evensen wrote: >> The firmware in the ZTE MF823/831/910 modems/mifis use OS fingerprinting to >> determine which type of device to export. In addition, these devices export

Re: [PATCH v8 04/11] net/mlx4_en: add support for fast rx drop bpf program

On Mon, Jul 18, 2016 at 2:48 PM, Thomas Graf wrote: > On 07/18/16 at 01:39pm, Tom Herbert wrote: >> On Mon, Jul 18, 2016 at 11:10 AM, Thomas Graf wrote: >> > I agree with that but I would like to keep the current per net_device >> > atomic properties. >> >> I don't

Re: [PATCH net-next] cdc_ether: Improve ZTE MF823/831/910 handling

On Mon, 2016-07-18 at 14:24 +0200, Kristian Evensen wrote: > The firmware in the ZTE MF823/831/910 modems/mifis use OS fingerprinting to > determine which type of device to export. In addition, these devices export > a REST API which can also be used to control the type of device. So far, on >

Re: [PATCH v8 04/11] net/mlx4_en: add support for fast rx drop bpf program

On 07/18/16 at 01:39pm, Tom Herbert wrote: > On Mon, Jul 18, 2016 at 11:10 AM, Thomas Graf wrote: > > I agree with that but I would like to keep the current per net_device > > atomic properties. > > I don't see that see that there is any synchronization guarantees > using xchg.

[PATCH net-next] cdc_ether: Improve ZTE MF823/831/910 handling

The firmware in the ZTE MF823/831/910 modems/mifis use OS fingerprinting to determine which type of device to export. In addition, these devices export a REST API which can also be used to control the type of device. So far, on Linux, the devices have been seen as RNDIS or CDC Ether. When CDC

Re: [PATCH 0/2] net: Consider fragmentation of udp tunneled skbs in 'ip_finish_output_gso'

This is the v3 of https://patchwork.ozlabs.org/patch/648790/

Re: [PATCH] sctp: load transport header after sk_filter

On Sat, Jul 16, 2016 at 05:33:15PM -0400, Willem de Bruijn wrote: > From: Willem de Bruijn > > Do not cache pointers into the skb linear segment across sk_filter. > The function call can trigger pskb_expand_head. > > Signed-off-by: Willem de Bruijn

[PATCH 1/2] net/ipv4: Introduce IPSKB_FRAG_SEGS bit to inet_skb_parm.flags

This flag indicates whether fragmentation of segments is allowed. Formerly this policy was hardcoded according to IPSKB_FORWARDED (set by either ip_forward or ipmr_forward). Cc: Hannes Frederic Sowa Cc: Florian Westphal Signed-off-by: Shmulik Ladkani

[PATCH 2/2] net: ip_finish_output_gso: If skb_gso_network_seglen exceeds MTU, allow segmentation for local udp tunneled skbs

Given: - tap0 and vxlan0 are bridged - vxlan0 stacked on eth0, eth0 having small mtu (e.g. 1400) Assume GSO skbs arriving from tap0 having a gso_size as determined by user-provided virtio_net_hdr (e.g. 1460 corresponding to VM mtu of 1500). After encapsulation these skbs have

<    1   2   3   >