From: Christian Widmer <cwidmer@iiic.ethz.ch>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hardware checksumming
Date: Thu, 23 Aug 2001 16:46:15 +0200 [thread overview]
Message-ID: <200108231446.f7NEkMk29499@mail.swissonline.ch> (raw)
In-Reply-To: <Pine.LNX.4.10.10108231354000.6061-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.10.10108231354000.6061-100000@coffee.psychology.mcmaster.ca>
On Thursday 23 August 2001 15:54, you wrote:
> > is hardware support by a NIC for checksum generation / offloading not
> > quite usless? the checksumming enging can only be used when UDP/TCP
> > packets are <= the MTU of the NIC (e.g 1500 bytes).
>
> checksums can be chained.
yes that might be easy fores belonging together come one after the other. so
the NIC ha transmit, since all chained frams only to trak one
fragmentet packet. but receiving is will become difficult since different
conections can arrive interleaved. something else: the NIC needs quite
a lot of ram or huge fifios. if not it will have to transfer the data twice
through the PCI (checksumm are at the beginig of a packet not the
end). nobody did spend a second on thinking to implement all in hard-
ware when the interet protokol was desinged.
do you know any NIC that is capable of chaining? currenty i've a dp83820
on my desc and at the moment im not eaven shure if checksumming can
be chained over multiple descriptions (describing one single ethernet frame).
>
> > i expact that UDP/TCP packets are in general bigger than that or is
> > exactly
>
> TCP packets are certainly never larger than the MTU.
next parent reply other threads:[~2001-08-23 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10108231354000.6061-100000@coffee.psychology.mcmaster.ca>
2001-08-23 14:46 ` Christian Widmer [this message]
2001-08-23 14:58 ` Christian Widmer
2001-08-24 0:31 ` Alexey Kuznetsov
2001-08-24 8:01 ` Helge Hafting
2001-08-23 12:13 Christian Widmer
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=200108231446.f7NEkMk29499@mail.swissonline.ch \
--to=cwidmer@iiic.ethz.ch \
--cc=hahn@physics.mcmaster.ca \
--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
all inboxes | Powered by JetHome®