netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michał Mirosław" <mirqus@gmail.com>
To: Jiri Pirko <jpirko@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	shemminger@linux-foundation.org, eric.dumazet@gmail.com,
	greearb@candelatech.com
Subject: Re: [patch net-next-2.6] vlan: introduce ndo_vlan_[enable/disable]
Date: Sun, 17 Jul 2011 10:36:04 +0200	[thread overview]
Message-ID: <CAHXqBFL1s30DxxHk-1wEy1q48LvgbO+w4zXkOm0sAU61XONoVw@mail.gmail.com> (raw)
In-Reply-To: <20110717073022.GA2089@minipsycho.orion>

W dniu 17 lipca 2011 09:30 użytkownik Jiri Pirko <jpirko@redhat.com> napisał:
> Sat, Jul 16, 2011 at 04:14:36PM CEST, mirqus@gmail.com wrote:
>>2011/7/16 Jiri Pirko <jpirko@redhat.com>:
>>> Some devices are not able to enable/disable rx/tw vlan accel separately.
>>> they depend on ndo_vlan_rx_register to know if to enable of disable
>>> hw accel. And since ndo_vlan_rx_register is going to die soon,
>>> this must be resolved.
>>>
>>> One solution might be to enable accel on device start every time, even
>>> if there are no vlan up on. But this would change behaviour and might
>>> lead to possible regression (on older devices).
>>[...]
>>
>>Please describe the possible regression. As I see it, there won't be
>>any user visible change of behaviour - network code takes care of
>>reinserting VLAN tag when necessary. If you think that disabling tag
>>stripping is beneficial for cases where no VLANs are configured, it's
>>better to do that in netdev_fix_features() for devices which advertise
>>NETIF_F_HW_VLAN_RX in hw_features.
>
> Well I just wanted to preserve current behaviour which is that in many
> drivers vlan accel is enabled only if some vid is registered upon the
> device and it's disabled again when no vid is registered. I can see
> no way to do this with current code after removing ndo_vlan_rx_register.
>
> I expect unexpected

:-D

> ... problems on old cards when vlan accel would be
> enabled all the time, but maybe I'm wrong...

Device has no way of knowing how the system uses VLAN tags, stripped
or not. Any problems would be driver problems and since you're making
it all use generic code, bugs will hit all drivers simultaneously or
(preferably) won't happen at all.

> One idea is for device which do not support sepatate rx/tx vlan accel
> enabling/disabling they can probably use ndo_fix_features force to
> enable/disable rx/tx pair together. That would resolve the situation as
> well giving user possibility to turn off vlan accel in case of any issues.

That is exactly the idea behind ndo_fix_features.

Best Regards,
Michał Mirosław

  reply	other threads:[~2011-07-17  8:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-16 10:15 [patch net-next-2.6] vlan: introduce ndo_vlan_[enable/disable] Jiri Pirko
2011-07-16 14:14 ` Michał Mirosław
2011-07-17  7:30   ` Jiri Pirko
2011-07-17  8:36     ` Michał Mirosław [this message]
2011-07-17 19:44       ` Jiri Pirko
2011-07-17 21:06         ` Michał Mirosław
2011-07-18  7:13           ` Jiri Pirko
2011-07-19  7:24             ` Michał Mirosław
2011-07-19  8:13               ` Jiri Pirko
2011-07-19  8:24                 ` Michał Mirosław
2011-07-19  8:27                   ` Michał Mirosław
2011-07-19 10:51                   ` Jiri Pirko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHXqBFL1s30DxxHk-1wEy1q48LvgbO+w4zXkOm0sAU61XONoVw@mail.gmail.com \
    --to=mirqus@gmail.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=greearb@candelatech.com \
    --cc=jpirko@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).