Bug#949863: #949863: please enable CONFIG_NET_SWITCHDEV

2020-11-05 Thread Vasudev Kamath
Vasudev Kamath  writes:

> Salvatore Bonaccorso  writes:
>
>> Hi 
>>
>> On Tue, Sep 15, 2020 at 02:00:51PM +0530, Vasudev Kamath wrote:
>>> Tzafrir Cohen  writes:
>>> 
>>> > Hi,
>>> >
>>> > A patch for fix of the regression is in 4.19.145 (commit 
>>> > 044be307e550b4532960eadabfb6942de96751f0  "net/mlx5e: Don't support phys 
>>> > switch id if not in switchdev mode").
>>> >
>>> > Please enable CONFIG_NET_SWITCHDEV once this is merged to the Buster 
>>> > kernel tree.
>>> >
>>> > -- Tzafrir
>>> 
>>> I just created another ticket as this bug is already archived [1]. And
>>> mail is not getting tracked in the BTS.
>>> 
>>> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970350
>>
>> Please have look at 
>> https://salsa.debian.org/kernel-team/linux/-/merge_requests/278 
>>
>> Still it should be evaluated if this has no other impact as it was
>> previously only enabled for armhf.
>
> We are already using this in our production with custom compiled kernel
> based on kernel in 10.4.(one with regression issue still present but
> workaround done manually) (Currently we have 50+ machines running  this
> and will eventually increase it).
>
> I will check this with current buster kernel from 10.5 where regression
> issue fix is applied and update here.

I compiled 10.6 kernel 4.19.152 with your MR patch and tested on our
setup. I can confirm no more regression issue is found on both network
setup we use (bonding and non-bonding).

As for the NET_SWITCHDEV we have this enabled in our production machine
from kernel compiled in 10.3 with this patch. And its been running for 2
months or so without any issue.

Please consider merging this patch and release it as part of Debian 10.7
release.

Cheers,
Vasudev



Bug#949863: #949863: please enable CONFIG_NET_SWITCHDEV

2020-11-01 Thread Vasudev Kamath
Salvatore Bonaccorso  writes:

> Hi 
>
> On Tue, Sep 15, 2020 at 02:00:51PM +0530, Vasudev Kamath wrote:
>> Tzafrir Cohen  writes:
>> 
>> > Hi,
>> >
>> > A patch for fix of the regression is in 4.19.145 (commit 
>> > 044be307e550b4532960eadabfb6942de96751f0  "net/mlx5e: Don't support phys 
>> > switch id if not in switchdev mode").
>> >
>> > Please enable CONFIG_NET_SWITCHDEV once this is merged to the Buster 
>> > kernel tree.
>> >
>> > -- Tzafrir
>> 
>> I just created another ticket as this bug is already archived [1]. And
>> mail is not getting tracked in the BTS.
>> 
>> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970350
>
> Please have look at 
> https://salsa.debian.org/kernel-team/linux/-/merge_requests/278 
>
> Still it should be evaluated if this has no other impact as it was
> previously only enabled for armhf.

We are already using this in our production with custom compiled kernel
based on kernel in 10.4.(one with regression issue still present but
workaround done manually) (Currently we have 50+ machines running  this
and will eventually increase it).

I will check this with current buster kernel from 10.5 where regression
issue fix is applied and update here.

Regards,
Vasudev



Bug#949863: #949863: please enable CONFIG_NET_SWITCHDEV

2020-10-31 Thread Salvatore Bonaccorso
Hi 

On Tue, Sep 15, 2020 at 02:00:51PM +0530, Vasudev Kamath wrote:
> Tzafrir Cohen  writes:
> 
> > Hi,
> >
> > A patch for fix of the regression is in 4.19.145 (commit 
> > 044be307e550b4532960eadabfb6942de96751f0  "net/mlx5e: Don't support phys 
> > switch id if not in switchdev mode").
> >
> > Please enable CONFIG_NET_SWITCHDEV once this is merged to the Buster 
> > kernel tree.
> >
> > -- Tzafrir
> 
> I just created another ticket as this bug is already archived [1]. And
> mail is not getting tracked in the BTS.
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970350

Please have look at 
https://salsa.debian.org/kernel-team/linux/-/merge_requests/278 

Still it should be evaluated if this has no other impact as it was
previously only enabled for armhf.

Regards,
Salvatore



Bug#949863: #949863: please enable CONFIG_NET_SWITCHDEV

2020-09-15 Thread Vasudev Kamath
Tzafrir Cohen  writes:

> Hi,
>
> A patch for fix of the regression is in 4.19.145 (commit 
> 044be307e550b4532960eadabfb6942de96751f0  "net/mlx5e: Don't support phys 
> switch id if not in switchdev mode").
>
> Please enable CONFIG_NET_SWITCHDEV once this is merged to the Buster 
> kernel tree.
>
> -- Tzafrir

I just created another ticket as this bug is already archived [1]. And
mail is not getting tracked in the BTS.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970350



Bug#949863: #949863: please enable CONFIG_NET_SWITCHDEV

2020-09-15 Thread Tzafrir Cohen

Hi,

A patch for fix of the regression is in 4.19.145 (commit 
044be307e550b4532960eadabfb6942de96751f0  "net/mlx5e: Don't support phys 
switch id if not in switchdev mode").


Please enable CONFIG_NET_SWITCHDEV once this is merged to the Buster 
kernel tree.


-- Tzafrir



Bug#949863: #949863: please enable CONFIG_NET_SWITCHDEV

2020-01-30 Thread Tzafrir Cohen
Also: please consider this change for inclusion in a stable update, if
possible.

Thanks



Bug#949863: #949863: please enable CONFIG_NET_SWITCHDEV

2020-01-29 Thread Tzafrir Cohen
Update:

adding CONFIG_NET_SWITCHDEV adds the following extra config items
(amd64, checked kernels 5.4 and 5.4):

CONFIG_MLX5_ESWITCH=y
CONFIG_MLX5_SW_STEERING=y
CONFIG_NFP_APP_FLOWER=y
CONFIG_NFP_APP_ABM_NIC=y

The following two are added but disabled by default.

# CONFIG_MSCC_OCELOT_SWITCH is not set
# CONFIG_ROCKER is not set


CONFIG_NET_SWITCHDEV is currently only enabled on armhf . I believe it
should be enabled on all architectures.

-- Tzafrir

On 26/01/2020 11:21, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
> 
> You can follow progress on this Bug here: 949863: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949863.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  Debian Kernel Team 
> 
> If you wish to submit further information on this problem, please
> send it to 949...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>