From: Madoka Komatsubara <m-komatsubara@ab.jp.nec.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
Hiroshi Baba <h-baba@ax.jp.nec.com>
Subject: Unable to receive multicast packet on VF
Date: Fri, 28 Mar 2014 11:49:05 +0000 [thread overview]
Message-ID: <9DE5760509B7974286F38D93BF31DD62C7D0B8@BPXM13GP.gisp.nec.co.jp> (raw)
Hi all,
We would like to use multicast packet on the guest with Intel 82599EB SR-IOV.
However, the document says that adding the multicast MAC address to the VF
is allowed during PF initialization only. (Please refer to the URL below.)
It means that we couldn't handle dynamically allocated multicast address.
On the other hand,
>From the data sheet, 82599EB has Multicast Promiscuous mode.
We could enable it on PF and all multicast packets are delivered to every VF.
That doesn't seem good, because each guest has to handle unnecessary packet.
Isn't it good to have a feature to add specific multicast address to VF?
Does anyone know that issue or the solution?
<http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/82599-10-gbe-controller-datasheet.pdf>
page585
section 8.2.3.7.7
"This table should be initialized by software before transmit and receive are enabled."
Regards,
Madoka Komatsubara
WARNING: multiple messages have this Message-ID (diff)
From: Madoka Komatsubara <m-komatsubara@ab.jp.nec.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
Hiroshi Baba <h-baba@ax.jp.nec.com>
Subject: Unable to receive multicast packet on VF
Date: Fri, 28 Mar 2014 11:49:05 +0000 [thread overview]
Message-ID: <9DE5760509B7974286F38D93BF31DD62C7D0B8@BPXM13GP.gisp.nec.co.jp> (raw)
Hi all,
We would like to use multicast packet on the guest with Intel 82599EB SR-IOV.
However, the document says that adding the multicast MAC address to the VF
is allowed during PF initialization only. (Please refer to the URL below.)
It means that we couldn't handle dynamically allocated multicast address.
On the other hand,
>From the data sheet, 82599EB has Multicast Promiscuous mode.
We could enable it on PF and all multicast packets are delivered to every VF.
That doesn't seem good, because each guest has to handle unnecessary packet.
Isn't it good to have a feature to add specific multicast address to VF?
Does anyone know that issue or the solution?
<http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/82599-10-gbe-controller-datasheet.pdf>
page585
section 8.2.3.7.7
"This table should be initialized by software before transmit and receive are enabled."
Regards,
Madoka Komatsubara
------------------------------------------------------------------------------
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next reply other threads:[~2014-03-28 11:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 11:49 Madoka Komatsubara [this message]
2014-03-28 11:49 ` Unable to receive multicast packet on VF Madoka Komatsubara
2014-03-28 20:54 ` Skidmore, Donald C
2014-03-28 20:54 ` Skidmore, Donald C
2014-04-02 9:04 ` Madoka Komatsubara
2014-04-02 9:04 ` Madoka Komatsubara
2014-04-11 9:58 ` Madoka Komatsubara
2014-04-11 9:58 ` Madoka Komatsubara
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=9DE5760509B7974286F38D93BF31DD62C7D0B8@BPXM13GP.gisp.nec.co.jp \
--to=m-komatsubara@ab.jp.nec.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=h-baba@ax.jp.nec.com \
--cc=h-shimamoto@ct.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.