From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
Cc: "Or Gerlitz" <gerlitz.or@gmail.com>,
"vyasevic@redhat.com" <vyasevic@redhat.com>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"Choi, Sy Jong" <sy.jong.choi@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"David Laight" <David.Laight@aculab.com>,
"Hayato Momma" <h-momma@ce.jp.nec.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Edward Cree" <ecree@solarflare.com>,
"Bjørn Mork" <bjorn@mork.no>
Subject: Re: [PATCH v3 1/3] ixgbe, ixgbevf: Add new mbox API to enable MC promiscuous mode
Date: Wed, 08 Apr 2015 13:43:21 -0700 [thread overview]
Message-ID: <1428525801.2579.6.camel@jtkirshe-mobl> (raw)
In-Reply-To: <7F861DC0615E0C47A872E6F3C5FCDDBD05E7CD29@BPXM14GP.gisp.nec.co.jp>
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]
On Wed, 2015-04-08 at 05:36 +0000, Hiroshi Shimamoto wrote:
> From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
>
> The limitation of the number of multicast address for VF is not enough
> for the large scale server with SR-IOV feature.
> IPv6 requires the multicast MAC address for each IP address to handle
> the Neighbor Solicitation message.
> We couldn't assign over 30 IPv6 addresses to a single VF interface.
>
> The easy way to solve this is enabling multicast promiscuous mode.
> It is good to have a functionality to enable multicast promiscuous
> mode
> for each VF from VF driver.
>
> This patch introduces the new mbox API, IXGBE_VF_SET_MC_PROMISC, to
> enable/disable multicast promiscuous mode in VF. If multicast
> promiscuous mode is enabled the VF can receive all multicast packets.
>
> With this patch, the ixgbevf driver automatically enable multicast
> promiscuous mode when the number of multicast addresses is over than
> 30
> if possible.
>
> Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
> Reviewed-by: Hayato Momma <h-momma@ce.jp.nec.com>
> CC: Choi, Sy Jong <sy.jong.choi@intel.com>
> ---
>
> This adds new mbox API, but doesn't change the version because
> v1.3 was newly added in the current dev-queue.
> Is that okay, or shall I increment the version?
>
> drivers/net/ethernet/intel/ixgbe/ixgbe.h | 1 +
> drivers/net/ethernet/intel/ixgbe/ixgbe_mbx.h | 2 +
> drivers/net/ethernet/intel/ixgbe/ixgbe_sriov.c | 76
> +++++++++++++++++++++++
> drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c | 3 +
> drivers/net/ethernet/intel/ixgbevf/mbx.h | 2 +
> drivers/net/ethernet/intel/ixgbevf/vf.c | 27 +++++++-
> drivers/net/ethernet/intel/ixgbevf/vf.h | 1 +
> 7 files changed, 111 insertions(+), 1 deletion(-)
I will add this to my queue, thanks Hiroshi.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-04-08 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 5:36 [PATCH v3 1/3] ixgbe, ixgbevf: Add new mbox API to enable MC promiscuous mode Hiroshi Shimamoto
2015-04-08 20:43 ` Jeff Kirsher [this message]
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=1428525801.2579.6.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=David.Laight@aculab.com \
--cc=bjorn@mork.no \
--cc=e1000-devel@lists.sourceforge.net \
--cc=ecree@solarflare.com \
--cc=gerlitz.or@gmail.com \
--cc=h-momma@ce.jp.nec.com \
--cc=h-shimamoto@ct.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sy.jong.choi@intel.com \
--cc=vyasevic@redhat.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