netdev - Re: [net-next-2.6 PATCH 06/13] igb: move all multicast addresses into multicast table array

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0907241053200.24126@tyr.diku.dk>
Date:	Fri, 24 Jul 2009 10:57:03 +0200 (CEST)
From:	Jesper Dangaard Brouer <hawk@...u.dk>
To:	Alexander Duyck <alexander.h.duyck@...el.com>
Cc:	"David S. Miller" <davem@...emloft.net>,
	netdev <netdev@...r.kernel.org>,
	Jeff Kirsher <jeffrey.t.kirsher@...el.com>, gospo@...hat.com
Subject: Re: [net-next-2.6 PATCH 06/13] igb: move all multicast addresses
 into multicast table array


On Thu, 23 Jul 2009, Jeff Kirsher wrote:

> From: Alexander Duyck <alexander.h.duyck@...el.com>
>
> This patch moves all of the multicast addresses out of the free Receive
> address registers and instead programs them all into the multicast table
> array.  As a result the multicast filtering may not be as precise, but it
> also greatly reduces the overhead for multicast addresses.

What do you mean by "the multicast filtering may not be as precise" ?

I'm planning to use these NICs for multicast traffic (both routing and 
monitoring).  Is there any precausing I need to be aware of?

Hilsen
   Jesper Brouer

--
-------------------------------------------------------------------
MSc. Master of Computer Science
Dept. of Computer Science, University of Copenhagen
Author of http://www.adsl-optimizer.dk
-------------------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html