netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: sarveshwarb@serverengines.com, netdev@vger.kernel.org
Subject: Re: [PATCH] be2net: Adding support for 802.1ad (q-in-q mode)
Date: Thu, 23 Jul 2009 18:33:05 +0200	[thread overview]
Message-ID: <4A6890C1.2000108@trash.net> (raw)
In-Reply-To: <20090723.092301.115261115.davem@davemloft.net>

David Miller wrote:
>> Sarveshwar Bandi wrote:
>>> The outer vlan is totally transparent to the host. It is used by the NIC 
>>> to demux packets across multiple pci network functions. Currently the 
>>> outer vlan tags are configured on the NIC by OEM provided utilities.
>> I see. A proper changelog entry would have explained that and avoided
>> all this confusion. Not that I think using another tool for this is a
>> good solution, but no objections from a functional POV.
> 
> Using OEM tools makes no sense, there should be something like an
> ethtool interface for changing this setting and appropriate changes
> to the common userland tools to provide access to them.
> 
> I'm not putting this change in until there is common infrastructure
> submitted to common tools to control this configuration.

Thanks, thats my opinion as well. But I think we should handle
Q-in-Q using the VLAN netlink API and iproute instead of ethtool
for consistency.

  reply	other threads:[~2009-07-23 16:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23  8:26 [PATCH] be2net: Adding support for 802.1ad (q-in-q mode) Sarveshwar Bandi
2009-07-23  8:47 ` Patrick McHardy
2009-07-23  9:02   ` Sarveshwar Bandi
2009-07-23  9:07     ` Patrick McHardy
2009-07-23  9:20       ` Sarveshwar Bandi
2009-07-23  9:25         ` Patrick McHardy
2009-07-23  9:45           ` Sarveshwar Bandi
2009-07-23  9:48             ` Patrick McHardy
2009-07-23 10:05               ` Sarveshwar Bandi
2009-07-23 10:12                 ` Patrick McHardy
2009-07-23 16:23                   ` David Miller
2009-07-23 16:33                     ` Patrick McHardy [this message]
2009-07-23 17:01                       ` David Miller

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=4A6890C1.2000108@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=sarveshwarb@serverengines.com \
    /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).