From: "David S. Miller" <davem@redhat.com>
To: jgarzik@mandrakesoft.com
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: Updated zerocopy patch up on kernel.org
Date: Tue, 9 Jan 2001 17:20:08 -0800 [thread overview]
Message-ID: <200101100120.RAA07805@pizda.ninka.net> (raw)
In-Reply-To: <3A5BB985.8A249BE1@mandrakesoft.com> (message from Jeff Garzik on Tue, 09 Jan 2001 20:23:17 -0500)
In-Reply-To: <200101100055.QAA07674@pizda.ninka.net> <3A5BB985.8A249BE1@mandrakesoft.com>
Date: Tue, 09 Jan 2001 20:23:17 -0500
From: Jeff Garzik <jgarzik@mandrakesoft.com>
Is there any value to supporting fragments in a driver which
doesn't do hardware checksumming? IIRC Alexey had a patch to do
such for Tulip, but I don't see it in the above patchset.
I'm actually considering making the SG w/o hwcsum situation illegal.
Basically, with SG only, you can run into some problems.
We don't prevent anyone from making modifications to the
paged data, we just grab references to the pages.
This works perfectly fine when the card does the checksumming,
the card DMAs a snapshot of the data into it's internal buffers,
checksums that local snapshot of the data, and the checksum is fine.
If, on the other hand, we're doing this in software, we can send out
packets with bad checksums. The next retransmit could fix it up, but
this is a horrible scheme quality of implementation wise.
Later,
David S. Miller
davem@redhat.com
-
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-10 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 1:23 Jeff Garzik
2001-01-10 0:55 ` David S. Miller
2001-01-10 1:20 ` David S. Miller [this message]
2001-01-11 10:41 ` Ingo Molnar
2001-01-11 4:33 ` David S. Miller
2001-01-11 10:38 ` Ingo Molnar
2001-01-11 12:47 ` Andrew Morton
2001-01-13 6:46 ` Anton Blanchard
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=200101100120.RAA07805@pizda.ninka.net \
--to=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®