From: Or Gerlitz <or.gerlitz@gmail.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, gospo@redhat.com,
Mitch Williams <mitch.a.williams@intel.com>,
Or Gerlitz <ogerlitz@voltaire.com>
Subject: Re: [net-next-2.6 PATCH 2/5] if_link: Add SR-IOV configuration methods
Date: Sun, 31 Jan 2010 16:25:43 +0200 [thread overview]
Message-ID: <15ddcffd1001310625k3a1c1010w57e7cf62986c56ef@mail.gmail.com> (raw)
In-Reply-To: <20100130103947.26633.78452.stgit@localhost.localdomain>
Jeff Kirsher wrote:
> +struct ifla_vf_vlan {
> + __u32 vf;
> + __s32 vlan; /* 0 - 4095, -1 disables VLAN filter */
> +};
Jeff,
In the same manner that vconfig does for 8021q devices, except for VID
there's a need
to let the user control on the egress qos mapping (vlan priority bits)
per VF (I don't think it
need to go per skb priority). Where for NIC HW which supports setting
the VID only, the
packets will be marked with a default priority.
Or.
next prev parent reply other threads:[~2010-01-31 14:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 10:39 [net-next-2.6 PATCH 1/5] pci: Add SR-IOV convenience functions and macros Jeff Kirsher
2010-01-30 10:39 ` [net-next-2.6 PATCH 2/5] if_link: Add SR-IOV configuration methods Jeff Kirsher
2010-01-31 14:25 ` Or Gerlitz [this message]
2010-02-01 19:33 ` Williams, Mitch A
2010-02-02 5:16 ` Or Gerlitz
2010-02-02 16:45 ` Williams, Mitch A
2010-02-04 1:36 ` David Miller
2010-01-30 10:40 ` [net-next-2.6 PATCH 3/5] net: Add netdev ops for SR-IOV configuration Jeff Kirsher
2010-02-03 22:00 ` Ben Hutchings
2010-01-30 10:40 ` [net-next-2.6 PATCH 4/5] rtnetlink: Add VF config code to rtnetlink Jeff Kirsher
2010-01-30 10:40 ` [net-next-2.6 PATCH 5/5] igb: support for VF configuration tools Jeff Kirsher
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=15ddcffd1001310625k3a1c1010w57e7cf62986c56ef@mail.gmail.com \
--to=or.gerlitz@gmail.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@voltaire.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).