From: Greg KH <greg@kroah.com>
To: Divy Le Ray <divy@chelsio.com>
Cc: Ben Greear <greearb@candelatech.com>,
Jeff Garzik <jeff@garzik.org>, NetDev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] cxgb - driver fixes.
Date: Tue, 11 Dec 2007 14:47:16 -0800 [thread overview]
Message-ID: <20071211224716.GA17643@kroah.com> (raw)
In-Reply-To: <4751ED97.5090804@chelsio.com>
On Sat, Dec 01, 2007 at 03:26:15PM -0800, Divy Le Ray wrote:
> Ben Greear wrote:
>> Divy Le Ray wrote:
>>> Jeff,
>>>
>>> I'm submitting a patch series for inclusion in 2.6.24 for the cxgb
>>> driver.
>>> The patches are built against Linus'git tree.
>>>
>>> Here is a brief description:
>>> - Ensure that GSO skbs have enough headroom before encapsulating them,
>>> - Fix a crash in NAPI mode,
>>> - Fix statistics accounting and report.
>>
>> We ran pktgen overnight on 2.6.23 with patch 1 and 3 applied (patch 2
>> not needed on .23 it seems) and it was stable at about 1.5Gbps
>> bi-directional
>> using 1500 MTU sized frames.
>>
>> We'll run some more tests with user-space TCP & UDP today, but it looks
>> good
>> so far.
>>
>> Perhaps these patches should be considered for .23 stable as well?
>>
>> Thanks,
>> Ben
>>
>
> Yes, patches 1 and 3 could be considered for .22 and .23-stable, along with
> the previous fix:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=7de6af0f23b25df8da9719ecae1916b669d0b03d
Can you send all of the individual patches you wish to have applied to
the -stable tree to stable@kernel.org so that we can properly determine
exactly which patches you are referring to?
Also, make sure they are already in Linus's tree before telling us about
them.
thanks,
greg k-h
prev parent reply other threads:[~2007-12-11 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 21:28 [PATCH 0/3] cxgb - driver fixes Divy Le Ray
2007-11-29 18:25 ` Ben Greear
2007-12-01 23:26 ` Divy Le Ray
2007-12-11 22:47 ` Greg KH [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=20071211224716.GA17643@kroah.com \
--to=greg@kroah.com \
--cc=divy@chelsio.com \
--cc=greearb@candelatech.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--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).