From: Anton Blanchard <anton@samba.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] TSO Reloaded
Date: Fri, 6 May 2005 14:36:53 +1000 [thread overview]
Message-ID: <20050506043653.GD8255@krispykreme> (raw)
In-Reply-To: <20050504230731.12be1bc3.davem@davemloft.net>
Hi Dave,
> Ok, here it is, first draft of the new TSO handling
> I promised so long ago :-) I was lazy and waited until
> today to implement the entire thing.
I fired off socklib (just a TCP stream test) and things look much
better. I dumped the size of the data+frags for each packet that the
e1000 created. It looks like frags are working in multiples of MTU, but
we also have to split when we hit page boundaries. Is this expected?
BTW the 4 bytes at the end is due to an e1000 workaround for a hw bug.
Thanks for working on this :)
Anton
data: 42 frags:
data: 74 frags:
data: 66 frags: 1448 1444 4
data: 66 frags: 1024 424 1444 4
data: 66 frags: 1448 512 932 4
data: 66 frags: 1448 1444 4
data: 66 frags: 1448
data: 66 frags: 1448 1024 424 1448 1448 512 936 1444 4
data: 66 frags: 1448 1444 4
data: 66 frags: 1448 1024 420 4
data: 66 frags: 1448 1444 4
data: 66 frags: 512 936 1448 1448 1448 1448 1024 424 1448 1448 512 936 1444 4
data: 66 frags: 1448 1448 1444 4
data: 66 frags: 1024 424 1448 1448 512 936 1448 1448 1444 4
data: 66 frags: 1448 1024 424 1448 1448 372 4
data: 66 frags: 128 1320 1448 1152 296 1448 1448 640 808 1444 4
data: 66 frags: 1448 128 1320 1444 4
data: 66 frags: 1152 296 1448 1448 640 804 4
data: 66 frags: 1448 1448 128 1316 4
data: 66 frags: 1448 1152 296 1444 4
data: 66 frags: 1448 640 808 1448 1448 128 1320 1448 1152 296 1448 1448 640 808 1448 1444 4
data: 66 frags: 128 1320 1448 1152 296 1448 1444 4
data: 66 frags: 640 808 1448 1444 4
data: 66 frags: 128 1320 1448 1152 296 1448 1448 372 4
data: 66 frags: 256 1192 1448 1280 168 1448 1448 768 680 1448 1448 256 1192 1448 1280 168 1444 4
data: 66 frags: 1448 768 680 1448 1444 4
data: 66 frags: 256 1192 1448 1280 168 1448 1444 4
next prev parent reply other threads:[~2005-05-06 4:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 6:07 [PATCH] TSO Reloaded David S. Miller
2005-05-05 22:35 ` David S. Miller
2005-05-05 22:56 ` Jon Mason
[not found] ` <20050505154955.0dcb4b38.davem@davemloft.net>
2005-05-06 3:53 ` Jon Mason
2005-05-05 23:11 ` Anton Blanchard
2005-05-05 23:14 ` David S. Miller
2005-05-06 1:03 ` Anton Blanchard
2005-05-05 23:18 ` Nivedita Singhvi
2005-05-05 23:24 ` Stephen Hemminger
2005-05-05 23:16 ` David S. Miller
2005-05-06 3:20 ` Leonid Grossman
2005-05-06 3:30 ` David S. Miller
2005-05-06 14:09 ` Leonid Grossman
2005-05-06 4:36 ` Anton Blanchard [this message]
2005-05-06 5:45 ` Anton Blanchard
2005-05-06 6:13 ` David S. Miller
2005-05-06 7:10 ` Anton Blanchard
2005-05-06 8:19 ` David S. Miller
2005-05-06 8:36 ` Anton Blanchard
2005-05-18 2:26 ` John Heffner
2005-05-18 2:28 ` David S. Miller
2005-05-18 2:51 ` John Heffner
2005-05-18 3:00 ` David S. Miller
2005-05-18 3:47 ` John Heffner
2005-05-18 5:59 ` David S. Miller
2005-05-18 13:48 ` John Heffner
[not found] <20050506123411.7073cf15.davem@davemloft.net>
2005-05-07 4:48 ` Leonid Grossman
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=20050506043653.GD8255@krispykreme \
--to=anton@samba.org \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
/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).