Re: [RFC net-next] net: Build IPv6 into kernel by default

2015-07-12 Thread YOSHIFUJI Hideaki
Hi, David Miller wrote: > From: Tom Herbert > Date: Thu, 9 Jul 2015 13:42:29 -0700 > >> This patch makes the default to build IPv6 into the kernel. IPv6 >> now has significant traction and any remaining vestiges of IPv6 >> not being provided parity with IPv4 should be swept away. IPv6 is now >>

Re: [PATCH net-next v2] ipv6: Do not iterate over all interfaces when finding source address on specific interface.

2015-07-12 Thread YOSHIFUJI Hideaki
Hi, Erik Kline wrote: > Hmm, when I run a UML linux with this patch (which, I'm ashamed to > say, I failed to do before) I get these kinds of errors: > > unregister_netdevice: waiting for to become free. > Usage count = 1 > unregister_netdevice: waiting for to become free. > Usage count

[GIT] Networking

2015-07-12 Thread David Miller
//git.kernel.org/pub/scm/linux/kernel/git/davem/net for you to fetch changes up to cee9f6d0186a586c8023bc91c8a4cf8a088855e5: Merge tag 'linux-can-fixes-for-4.2-20150712' of git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-c

RE: [PATCH] bnx2x: Update to FW version 7.12.30

2015-07-12 Thread Yuval Mintz
> > The new FW will allow us to utilize some new features in our driver, > > mainly adding vlan filtering offload and vxlan offload support. > > > > In addition, this fixes several issues: > > 1. Packets from a VF with pvid configured which were sent with a > >different vlan were transmitted in

Re: pull-request: can 2015-07-12

2015-07-12 Thread David Miller
From: Marc Kleine-Budde Date: Sun, 12 Jul 2015 21:18:03 +0200 > this is a pull request of 8 patchs for net/master. > > Sergei Shtylyov contributes 5 patches for the rcar_can driver, fixing the IRQ > check and several info and error messages. There are two patches by J.D. > Schroeder and Roger Qu

[RFC PATCH 0/2] net: macb: Add mdio driver for accessing multiple phy devices

2015-07-12 Thread Punnaiah Choudary Kalluri
This patch is to add support for the design that has multiple ethernet mac controllers and single mdio bus connected to multiple phy devices. i.e mdio lines are connected to any of the ethernet mac controller and all the phy devices will be accessed using the phy maintenance interface in that mac c

Re: Fighting out-of-order reception with RPS?

2015-07-12 Thread Eric Dumazet
On Sun, 2015-07-12 at 21:15 +0200, Oliver Hartkopp wrote: > E.g. with > > skb_set_hash(skb, dev->ifindex, PKT_HASH_TYPE_L2); > > and > > echo f > /sys/class/net/can0/queues/rx-0/rps_cpus > > I get properly ordered CAN frames - even with netif_rx() processed skbs. I > just want to h

[RFC PATCH 2/2] net: macb: Add support for single mac managing more than one phy

2015-07-12 Thread Punnaiah Choudary Kalluri
Added support for single mac managing more than one phy Signed-off-by: Punnaiah Choudary Kalluri --- drivers/net/ethernet/cadence/macb.c | 25 - drivers/net/ethernet/cadence/macb.h |4 +++- 2 files changed, 23 insertions(+), 6 deletions(-) diff --git a/drivers/net/

[RFC PATCH 1/2] net: macb: Add mdio driver for accessing multiple phy devices

2015-07-12 Thread Punnaiah Choudary Kalluri
This patch is to add spoort for the design that has multiple ethernet mac controllers and single mdio bus connected to multiple phy devices. i.e mdio lines are connected to any of the ethernet mac controller and all the phy devices will be accessed using the phy maintainance interface in that mac c

RE: [RFC PATCH] net: macb: Add mdio driver for accessing multiple phy devices

2015-07-12 Thread Punnaiah Choudary Kalluri
Please ignore this patch series. Regards, Punnaiah > -Original Message- > From: Punnaiah Choudary Kalluri > [mailto:punnaiah.choudary.kall...@xilinx.com] > Sent: Monday, July 13, 2015 9:06 AM > To: nicolas.fe...@atmel.com; Michal Simek; Anirudha Sarangi; > da...@davemloft.net > Cc: Harini

[RFC PATCH 4/4] vhost: Add cgroup-aware creation of worker threads

2015-07-12 Thread Bandan Das
With the help of the cgroup function to compare groups introduced in the previous patch, this changes worker creation policy. If the new device belongs to different cgroups than any of the devices we are currently serving, we end up creating a new worker thread even if we haven't reached the devs_p

[RFC PATCH 3/4] cgroup: Introduce a function to compare cgroups

2015-07-12 Thread Bandan Das
This function takes two tasks and iterates through all hierarchies to check if they belong to the same cgroups. It ignores the check for default hierarchies or for hierarchies with no subsystems attached. This function will be used by the next patch to add rudimentary cgroup support with vhost work

[RFC PATCH 0/4] Shared vhost design

2015-07-12 Thread Bandan Das
Hello, There have been discussions on improving the current vhost design. The first attempt, to my knowledge was Shirley Ma's patch to create a dedicated vhost worker per cgroup. http://comments.gmane.org/gmane.linux.network/224730 Later, I posted a cmwq based approach for performance comparisio

[RFC PATCH 2/4] vhost: Limit the number of devices served by a single worker thread

2015-07-12 Thread Bandan Das
When the number of devices increase, the universal thread model (introduced in the preceding patch) may end up being the bottleneck. Moreover, a single worker thread also forces us to change cgroups based on the device we are serving. We introduce a worker pool struct that starts with one worker t

[RFC PATCH] net: macb: Add mdio driver for accessing multiple phy devices

2015-07-12 Thread Punnaiah Choudary Kalluri
This patch is to add spoort for the design that has multiple ethernet mac controllers and single mdio bus connected to multiple phy devices. i.e mdio lines are connected to any of the ethernet mac controller and all the phy devices will be accessed using the phy maintainance interface in that mac c

[RFC PATCH 1/4] vhost: Introduce a universal thread to serve all users

2015-07-12 Thread Bandan Das
vhost threads are per-device, but in most cases a single thread is enough. This change creates a single thread that is used to serve all guests. However, this complicates cgroups associations. The current policy is to attach the per-device thread to all cgroups of the parent process that the devic

[RFC PATCH 2/2] net: macb: Add support for single mac managing more than one phy

2015-07-12 Thread Punnaiah Choudary Kalluri
Added support for single mac managing more than one phy Signed-off-by: Punnaiah Choudary Kalluri --- drivers/net/ethernet/cadence/macb.c | 25 - drivers/net/ethernet/cadence/macb.h |4 +++- 2 files changed, 23 insertions(+), 6 deletions(-) diff --git a/drivers/net/

[RFC PATCH 0/2] net: macb: Add mdio driver for accessing multiple phy devices

2015-07-12 Thread Punnaiah Choudary Kalluri
This patch is to add support for the design that has multiple ethernet mac controllers and single mdio bus connected to multiple phy devices. i.e mdio lines are connected to any of the ethernet mac controller and all the phy devices will be accessed using the phy maintenance interface in that mac c

Re: [PATCH v2] net: dsa: mv88e6xxx: add write access to debugfs regs file

2015-07-12 Thread David Miller
From: Vivien Didelot Date: Sun, 12 Jul 2015 21:39:30 -0400 (EDT) > I hardly see how this debug interface can be made generic to other > DSA drivers, since the format of hardware tables or some registers > seem very specific to the switch chip. You feel this way because you are focusing on regist

Re: Fighting out-of-order reception with RPS?

2015-07-12 Thread David Miller
From: Oliver Hartkopp Date: Sun, 12 Jul 2015 21:15:36 +0200 > Just some remarks about CAN and CAN frames as you suggest GRO which is > completely pointless for CAN. GRO may be pointless for CAN, but NAPI _definitely_ is useful for every single network device, period. So you should do NAPI for r

Re: [PATCH v2] net: dsa: mv88e6xxx: add write access to debugfs regs file

2015-07-12 Thread Vivien Didelot
Hi David, On Jul 11, 2015, at 10:08 PM, David da...@davemloft.net wrote: > From: Vivien Didelot > Date: Sat, 11 Jul 2015 14:36:12 -0400 (EDT) > >> In the meantime, this is really useful for development. i.e. ensuring a good >> switchdev/DSA interaction without being able to read and write direc

Re: [PATCH v2] add stealth mode

2015-07-12 Thread Matteo Croce
2015-07-08 15:32 GMT+02:00 Austin S Hemmelgarn : > On 2015-07-06 15:44, Matteo Croce wrote: > Just to name a few that I know of off the top of my head: > 1. IP packets with any protocol number not supported by your current kernel > (these return a special ICMP message). Right, I'll handle them >

[PATCH net] rtnetlink: reject non-IFLA_VF_PORT attributes inside IFLA_VF_PORTS

2015-07-12 Thread Daniel Borkmann
Similarly as in commit 4f7d2cdfdde7 ("rtnetlink: verify IFLA_VF_INFO attributes before passing them to driver"), we have a double nesting of netlink attributes, i.e. IFLA_VF_PORTS only contains IFLA_VF_PORT that is nested itself. While IFLA_VF_PORTS is a verified attribute from ifla_policy[], we on

[PATCH] net: mvneta: fix refilling for Rx DMA buffers

2015-07-12 Thread Simon Guinot
On some Armada 370-based NAS, I have experimented kernel bugs and crashes when the mvneta Ethernet driver fails to refill Rx DMA buffers due to memory shortage. With the actual code, if the memory allocation fails while refilling a Rx DMA buffer, then the corresponding descriptor is let with the a

[PATCH 5/8] can: rcar_can: unify error messages

2015-07-12 Thread Marc Kleine-Budde
From: Sergei Shtylyov All the error messages in the driver but the ones from devm_clk_get() failures use similar format. Make those two messages consitent with others. Signed-off-by: Sergei Shtylyov Signed-off-by: Marc Kleine-Budde --- drivers/net/can/rcar_can.c | 5 +++-- 1 file changed,

[PATCH 3/8] can: rcar_can: fix typo in error message

2015-07-12 Thread Marc Kleine-Budde
From: Sergei Shtylyov Fix typo in the first error message printed by rcar_can_open(). Based on the original patch by Vladimir Barinov. Fixes: 862e2b6af941 ("can: rcar_can: support all input clocks") Reported-by: Vladimir Barinov Signed-off-by: Sergei Shtylyov Signed-off-by: Marc Kleine-Budde

[PATCH 2/8] can: rcar_can: print signed IRQ #

2015-07-12 Thread Marc Kleine-Budde
From: Sergei Shtylyov Printing IRQ # using "%x" and "%u" unsigned formats isn't quite correct as 'ndev->irq' is of type *int*, so the "%d" format needs to be used instead. While fixing this, beautify the dev_info() message in rcar_can_probe() a bit. Fixes: fd1159318e55 ("can: add Renesas R-C

[PATCH 4/8] can: rcar_can: print request_irq() error code

2015-07-12 Thread Marc Kleine-Budde
From: Sergei Shtylyov Also print the error code when the request_irq() call fails in rcar_can_open(), rewording the error message... Signed-off-by: Sergei Shtylyov Signed-off-by: Marc Kleine-Budde --- drivers/net/can/rcar_can.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --

[PATCH 6/8] can: c_can: Fix default pinmux glitch at init

2015-07-12 Thread Marc Kleine-Budde
From: "J.D. Schroeder" The previous change 3973c526ae9c (net: can: c_can: Disable pins when CAN interface is down) causes a slight glitch on the pinctrl settings when used. Since commit ab78029 (drivers/pinctrl: grab default handles from device core), the device core will automatically set the de

[PATCH 1/8] can: rcar_can: fix IRQ check

2015-07-12 Thread Marc Kleine-Budde
From: Sergei Shtylyov rcar_can_probe() regards 0 as a wrong IRQ #, despite platform_get_irq() that it calls returns negative error code in that case. This leads to the following being printed to the console when attempting to open the device: error requesting interrupt fffa because rcar_ca

[PATCH 7/8] ARM: dts: dra7x-evm: Prevent glitch on DCAN1 pinmux

2015-07-12 Thread Marc Kleine-Budde
From: Roger Quadros Driver core sets "default" pinmux on on probe and CAN driver sets "sleep" pinmux during register. This causes a small window where the CAN pins are in "default" state with the DCAN module being disabled. Change the "default" state to be like sleep so this glitch is avoided. A

[PATCH 8/8] can: replace timestamp as unique skb attribute

2015-07-12 Thread Marc Kleine-Budde
From: Oliver Hartkopp Commit 514ac99c64b "can: fix multiple delivery of a single CAN frame for overlapping CAN filters" requires the skb->tstamp to be set to check for identical CAN skbs. Without timestamping to be required by user space applications this timestamp was not generated which lead t

pull-request: can 2015-07-12

2015-07-12 Thread Marc Kleine-Budde
orted operations (2015-07-11 21:29:55 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git tags/linux-can-fixes-for-4.2-20150712 for you to fetch changes up to d3b58c47d330de8c29898fe9746f7530408f8a59: can: replace timestamp as uniqu

Re: Fighting out-of-order reception with RPS?

2015-07-12 Thread Oliver Hartkopp
Hello Eric, On 07/11/2015 06:35 AM, Eric Dumazet wrote: > On Fri, 2015-07-10 at 22:36 +0200, Oliver Hartkopp wrote: >> Hm. Doesn't sound like a good solution when there's a difference between NAPI >> and non-NAPI drivers in matters of OOO, right? > > Isn't OOO a problem for you ? Then you either

Re: [except_nonlink net-next]r8169:Add exception when missing link

2015-07-12 Thread Francois Romieu
Marian Corcodel : > Add exception when missing link because original function " > rtl8169_check_link_status" must be int instead of void. You explain why the patch is done this way but you don't explain why it is needed/useful. > commit 21d27973b264192a4ccd6488b1487f07293b11c8 > Author: Corcodel