From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
linux-wireless@vger.kernel.org
Subject: Re: net-next-2.6 is live
Date: Thu, 22 Jan 2009 19:17:26 -0800 [thread overview]
Message-ID: <9929d2390901221917s606489c3wfe77612c9c989433@mail.gmail.com> (raw)
In-Reply-To: <20090121.165820.171747430.davem@davemloft.net>
On Wed, Jan 21, 2009 at 4:58 PM, David Miller <davem@davemloft.net> wrote:
>
> Ok, I've pushed all of the patches I've applied for 2.6.30 off to:
>
> master.kernel.org:/pub/scm/linux/kernel/git/davem/net-next-2.6.git
>
> Enjoy.
> --
Dave, the net-next tree seems to be missing this patch...
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Mon, 19 Jan 2009 16:17:08 -0800
e1000e: drop lltx, remove unnecessary lock
LLTX is deprecated and complicated, don't use it. It was observed by Don Ash
<donash4@gmail.com> that e1000e was acquiring this lock in the NAPI cleanup
path. This is obviously a bug, as this is a leftover from when e1000
supported multiple tx queues and fake netdevs.
another user reported this to us and tested routing with the 2.6.27 kernel and
this patch and reported a 3.5 % improvement in packets forwarded in a
multi-port test on 82571 parts.
Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
--
Cheers,
Jeff
next prev parent reply other threads:[~2009-01-23 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 0:58 net-next-2.6 is live David Miller
2009-01-23 3:17 ` Jeff Kirsher [this message]
[not found] ` <9929d2390901221917s606489c3wfe77612c9c989433-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-23 7:39 ` 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=9929d2390901221917s606489c3wfe77612c9c989433@mail.gmail.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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).