From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>
Cc: daveboutcher@gmail.com, jesse.brandeburg@intel.com,
netdev@vger.kernel.org
Subject: Re: [PATCH] e1000: fix loss of multicast packets
Date: Mon, 23 Mar 2009 19:53:54 -0700 [thread overview]
Message-ID: <9929d2390903231953v463a3426jb6b698b0e9a4f51f@mail.gmail.com> (raw)
In-Reply-To: <20090323.010957.163908188.davem@davemloft.net>
On Mon, Mar 23, 2009 at 1:09 AM, David Miller <davem@davemloft.net> wrote:
> From: Dave Boutcher <daveboutcher@gmail.com>
> Date: Sun, 22 Mar 2009 13:05:19 -0500
>
>> On Fri, Mar 20, 2009 at 3:44 PM, Jesse Brandeburg
>> <jesse.brandeburg@intel.com> wrote:
>> > From: Jesse Brandeburg <jesse.brandeburg@intel.com>
>> > This driver fix prepares an array all at once in memory and programs it in
>> > one shot to the hardware, not requiring an "erase" cycle.
>> >
>> > Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
>> > CC: Dave Boutcher <daveboutcher@gmail.com>
>>
>> Jesse, I just with this patch in my e1000 environment and it works
>> great. Almost 1,000,000 packets exchanged with active
>> membership join/drops going on and no packets lost. Thanks
>> for the fast turnaround.
>
> Thanks for testing Dave.
>
> Intel folks, can we get this formally submitted soon?
>
> Thanks.
> --
Yes, I have it in my queue. It should be in the next series of fixes
I will be sending out.
--
Cheers,
Jeff
next prev parent reply other threads:[~2009-03-24 2:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090320204415.25109.57486.stgit@lindenhurst-2.jf.intel.com>
2009-03-22 18:05 ` [PATCH] e1000: fix loss of multicast packets Dave Boutcher
2009-03-23 8:09 ` David Miller
2009-03-24 2:53 ` Jeff Kirsher [this message]
2009-03-24 11:26 ` Dave Boutcher
2009-03-24 22:50 ` Jeff Kirsher
2009-04-03 2:00 Jeff Kirsher
2009-04-04 23:37 ` David Miller
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=9929d2390903231953v463a3426jb6b698b0e9a4f51f@mail.gmail.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=daveboutcher@gmail.com \
--cc=davem@davemloft.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).