lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <9DE5760509B7974286F38D93BF31DD62C7D0B8@BPXM13GP.gisp.nec.co.jp>
Date:	Fri, 28 Mar 2014 11:49:05 +0000
From:	Madoka Komatsubara <m-komatsubara@...jp.nec.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC:	Hiroshi Shimamoto <h-shimamoto@...jp.nec.com>,
	Hiroshi Baba <h-baba@...jp.nec.com>
Subject: Unable to receive multicast packet on VF

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ