From: Ion Badulescu <ionut@moisil.cs.columbia.edu>
To: kuznet@ms2.inr.ac.ru
Cc: linux-kernel@vger.kernel.org, andrewm@uow.EDU.AU (Andrew Morton)
Subject: Re: [UPDATE] Zerocopy patches, against 2.4.1-pre10
Date: Thu, 25 Jan 2001 12:28:19 -0800 [thread overview]
Message-ID: <200101252028.f0PKSJR02124@moisil.dev.hydraweb.com> (raw)
In-Reply-To: <200101251929.WAA10001@ms2.inr.ac.ru>
On Thu, 25 Jan 2001 22:29:14 +0300 (MSK), kuznet@ms2.inr.ac.ru wrote:
> Hello!
>
>> no problems. I simply mounted an NFS server with rsize=wsize=8192
>> and read a few files - I assume this is sufficient?
>
> This is orthogonal.
>
> Only TCP uses this and you need not to do something special
> to test it. Any TCP connection going through 3c tests it.
Well, yes and no. It's not quite orthogonal, because normally TCP
will never transmit fragmented packets, and it's precisely fragmented
packets that make the interesting case with a card that supports
hardware TCP/UDP checksums.
If the packets are not fragmented, then the card can just verify the
checksums and be done with it. However, with fragments, all it can
do is report a partial checksum to the driver and let the driver
(or the stack) combine those partial checksums into one complete
checksum once all fragments have arrived. At least that's what the
Starfire card does, maybe the 3com is different. :-)
Are we even bothering with the partial checksums at this point, or
are we falling back to CPU checksumming if the packet is fragmented?
And, on a related note: what's involved in making a driver
zerocopy-aware? I haven't looked too closely to the current patch,
but I was thinking of playing with the starfire driver, since I
have all the chipset docs..
Thanks,
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-25 20:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200101242123.NAA00986@pizda.ninka.net>
2001-01-25 1:40 ` [UPDATE] Zerocopy patches, against 2.4.1-pre10 Andrew Morton
2001-01-25 9:29 ` David S. Miller
2001-01-25 19:29 ` kuznet
2001-01-25 20:28 ` Ion Badulescu [this message]
2001-01-25 20:36 ` kuznet
2001-01-25 20:43 ` David S. Miller
2001-01-25 21:11 ` Ion Badulescu
2001-01-25 21:14 ` David S. Miller
2001-01-25 21:29 ` Steve Whitehouse
2001-01-25 21:38 ` David S. Miller
2001-01-31 16:04 ` Alan Cox
2001-03-11 20:55 ` NBD Fix (attempt #2) Steve Whitehouse
2001-01-26 6:06 ` [UPDATE] Zerocopy patches, against 2.4.1-pre10 Ion Badulescu
2001-01-26 13:13 ` David S. Miller
2001-01-26 20:43 ` Ion Badulescu
2001-01-27 0:55 ` Ion Badulescu
2001-01-27 18:39 ` kuznet
2001-01-27 21:18 ` Ion Badulescu
2001-01-30 6:02 ` David S. Miller
2001-01-26 19:43 ` kuznet
2001-01-29 22:02 ` David S. Miller
2001-01-26 1:27 ` Andrew Morton
2001-01-24 21:52 Jonathan Earle
2001-01-24 23:33 ` Peter Samuelson
-- strict thread matches above, loose matches on Subject: below --
2001-01-24 21:34 Jonathan Earle
2001-01-24 21:45 ` Mathieu Chouquet-Stringer
2001-01-31 22:42 ` Rogerio Brito
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=200101252028.f0PKSJR02124@moisil.dev.hydraweb.com \
--to=ionut@moisil.cs.columbia.edu \
--cc=andrewm@uow.EDU.AU \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@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