linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ion Badulescu <ionut@cs.columbia.edu>
To: "David S. Miller" <davem@redhat.com>
Cc: <kuznet@ms2.inr.ac.ru>, <linux-kernel@vger.kernel.org>,
	Andrew Morton <andrewm@uow.EDU.AU>
Subject: Re: [UPDATE] Zerocopy patches, against 2.4.1-pre10
Date: Thu, 25 Jan 2001 13:11:40 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.30.0101251253300.20615-100000@age.cs.columbia.edu> (raw)
In-Reply-To: <14960.36869.977528.642327@pizda.ninka.net>

On Thu, 25 Jan 2001, David S. Miller wrote:

>
> Ion Badulescu writes:
>  > 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.
>
> No it is not the interesting case for such cards.  I have a feeling
> you have no idea what you are talking about or who you are speaking
> to.  Alexey bascially implemented all of the zerocopy stuff in that
> patch, so it's a good bet that he has a good idea what is orthogonal
> or not.

Wrong feeling. :-) No, I know who Alexey is and I think I know what I'm
talking about, too. We're just talking about different things, RX vs TX.

Obviously there isn't much we can do with fragmented packets on TX. If
only the IP people had learned from Ethernet people about a good place for
a CRC/csum...

> On transmit, on transmit, that's all that matters on the hardware side
> with these changes, where the card does the checksumming for us.
> We've supported receive checksum verification from the hardware
> forever, long before these changes.

Hmm, I must have missed the CHECKSUM_HW stuff. Mea culpa. Not that many
drivers use it at this time, I see a grand total of 2 (hamachi and hme) in
2.4.0 -- and yes I know who wrote the hme driver, too. :)

>  > And, on a related note: what's involved in making a driver
>  > zerocopy-aware? I haven't looked too closely to the current patch,
>
> When you look closely at the current patch, you will see exactly what
> is required.  3 hardware drivers are ported there, and are to be used
> as examples.

Ok.

I'm just wondering, if a card supports sg but *not* TX csum, is it worth
it to make use of sg? eepro100 falls into this category..

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/

  reply	other threads:[~2001-01-25 21:12 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 19:29   ` kuznet
2001-01-25 20:28     ` Ion Badulescu
2001-01-25 20:36       ` kuznet
2001-01-25 20:43     ` David S. Miller
2001-01-25 21:11       ` Ion Badulescu [this message]
2001-01-26 19:43         ` kuznet
2001-01-29 22:02         ` David S. Miller
2001-01-25 21:14       ` David S. Miller
2001-01-25 21:29         ` Steve Whitehouse
2001-01-31 16:04           ` Alan Cox
2001-03-11 20:55             ` NBD Fix (attempt #2) Steve Whitehouse
2001-01-25 21:38         ` [UPDATE] Zerocopy patches, against 2.4.1-pre10 David S. Miller
2001-01-26  6:06         ` 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  1:27     ` Andrew Morton
2001-01-25  9:29 ` David S. Miller
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=Pine.LNX.4.30.0101251253300.20615-100000@age.cs.columbia.edu \
    --to=ionut@cs.columbia.edu \
    --cc=andrewm@uow.EDU.AU \
    --cc=davem@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).