netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jesse.brandeburg@intel.com
Cc: daveboutcher@gmail.com, dada1@cosmosbay.com,
	netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: Re: IGMP Join dropping multicast packets
Date: Wed, 18 Mar 2009 22:46:30 -0700 (PDT)	[thread overview]
Message-ID: <20090318.224630.262428741.davem@davemloft.net> (raw)
In-Reply-To: <alpine.WNT.2.00.0903181016120.5116@jbrandeb-desk1.amr.corp.intel.com>

From: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Date: Wed, 18 Mar 2009 10:24:18 -0700 (Pacific Daylight Time)

> Interesting, this code has been there for eons (and probably this 
> behavior) but that doesn't mean its not a problem.
> 
> We are in the process of figuring out if there are any hardware corner 
> cases to changing this code (particularly in e1000)
> 
> Initial thoughts are:
> 1) kcalloc an array that we then populate with the hash functions, and 
>    then program every location only once (never flush)
> 2) only program a single hash value each time a multicast is added (bad 
>    because we can't tell the difference in the list since the last time 
>    the OS gave us the list)
> 
> It really seems like this should be fixable, and I agree that the driver 
> behavior is far from optimal, however well entrenched.

Just do what tg3 does to fix this now, get fancy and "beautiful"
later.

      parent reply	other threads:[~2009-03-19  5:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14 20:16 IGMP Join dropping multicast packets Dave Boutcher
2009-03-15  2:37 ` Eric Dumazet
2009-03-16  2:04   ` Dave Boutcher
2009-03-16 19:01     ` Eric Dumazet
2009-03-17  7:08       ` Eric Dumazet
2009-03-18  3:50       ` Dave Boutcher
2009-03-18  7:38         ` Eric Dumazet
2009-03-18 17:24         ` Brandeburg, Jesse
2009-03-19  1:48           ` Dave Boutcher
2009-03-19  1:51           ` Dave Boutcher
2009-03-20 20:36             ` Brandeburg, Jesse
2009-03-19  5:46           ` David Miller [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=20090318.224630.262428741.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dada1@cosmosbay.com \
    --cc=daveboutcher@gmail.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jesse.brandeburg@intel.com \
    --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 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).