From: "Jeff V. Merkey" <jmerkey@soleranetworks.com>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Kernel Netdev Mailing List <netdev@vger.kernel.org>
Subject: Re: e1000 82571 Packet Splitting
Date: Tue, 22 Nov 2005 15:27:57 -0700 [thread overview]
Message-ID: <43839B6D.9060301@soleranetworks.com> (raw)
In-Reply-To: <4807377b0511221546h7a16c0a9p793e441197b23118@mail.gmail.com>
Jesse Brandeburg wrote:
>this should be on netdev.
>
>On 11/22/05, Jeff V. Merkey <jmerkey@soleranetworks.com> wrote:
>
>
>>I have noted that the e1000 driver is now supporting DMA splitting of
>>the packet header and payload into separate pages. I also noticed
>>that none of the config options enable it. Is anyone using this feature
>>at present and has it even been tested on Linux?
>>
>>
>
>The 6.2.15 driver off http://prdownloads.sf.net/e1000 will enable it
>by default. We've gone through our release approval, which includes
>quite a bit of testing.
>If the patches posted recently don't include that support, I missed
>something :-)
>
>This is only on the 82571 and greater hardware that packet split is
>supported, BTW.
>
>
>
Got it. I am merging packet capture support into the e1000 for DSFS for
direct cache DMA support. I noticed the two distinct fill routines
for the ring buffer. I have enabled DSFS for both with this driver. I
will post patches late tonight or in the morning for the 82571 support
for DSFS. I will
also be posting the patches for 2.6.12, 2.6.10. 2.6.14, Suse 9 and 10.0,
Red Hat ES/AS 3 and 4, and Fedora Core 2/3/4 by end of week with the
packet splitting capabilities with packet capture on DSFS. This is a
very good optimization and should come in handy for reducing header copies
in the protocol stacks.
Jeff
prev parent reply other threads:[~2005-11-22 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43838614.9080807@soleranetworks.com>
2005-11-22 23:46 ` e1000 82571 Packet Splitting Jesse Brandeburg
2005-11-22 22:27 ` Jeff V. Merkey [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=43839B6D.9060301@soleranetworks.com \
--to=jmerkey@soleranetworks.com \
--cc=jesse.brandeburg@gmail.com \
--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).