From: ebiederm@xmission.com (Eric W. Biederman)
To: "David S. Miller" <davem@redhat.com>
Cc: Werner Almesberger <werner@almesberger.net> jgarzik@pobox.com,
niv@us.ibm.com, netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: TOE brain dump
Date: 05 Aug 2003 11:25:57 -0600 [thread overview]
Message-ID: <m1ptjkuica.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20030804122632.65ba2122.davem@redhat.com>
"David S. Miller" <davem@redhat.com> writes:
> On Mon, 4 Aug 2003 16:24:33 -0300
> Werner Almesberger <werner@almesberger.net> wrote:
>
> > Eric W. Biederman wrote:
> > > There is one place in low latency communications that I can think
> > > of where TCP/IP is not the proper solution. For low latency
> > > communication the checksum is at the wrong end of the packet.
> >
> > That's one of the few things ATM's AAL5 got right.
>
> Let's recall how long the IFF_TRAILERS hack from BSD :-)
Putting the variable length headers on the end of a packet? Or
was that something other than RFC893?
I think IPv6 solves that much more cleanly by simply deleting them.
> > But in the end, I think it doesn't really matter.
>
> I tend to agree on this one.
>
> And on the transmit side if you have more than 1 pending TX frame, you
> can always be prefetching the next one into the fifo so that by the
> time the medium is ready all the checksum bits have been done.
For large data transmissions that happens.
> In fact I'd be surprised if current generation 1g/10g cards are not
> doing something like this.
Well at this point before I propose anything concrete I suspect I need
to profile some actual application and see how things go. But from a
very latency sensitive perspective, I would be surprised if the
problem goes away with faster technology.
For now I am happy just to insert the peculiar thought that latency
across the entire cluster/lan is of great importance to some
applications.
Eric
next prev parent reply other threads:[~2003-08-05 17:25 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 17:04 TOE brain dump Werner Almesberger
2003-08-02 17:32 ` Nivedita Singhvi
2003-08-02 18:06 ` Werner Almesberger
2003-08-02 19:08 ` Jeff Garzik
2003-08-02 21:49 ` Werner Almesberger
2003-08-03 6:40 ` Jeff Garzik
2003-08-03 17:57 ` Werner Almesberger
2003-08-03 18:27 ` Erik Andersen
2003-08-03 19:40 ` Larry McVoy
2003-08-03 20:13 ` David Lang
2003-08-03 20:30 ` Larry McVoy
2003-08-03 21:21 ` David Lang
2003-08-03 23:44 ` Larry McVoy
2003-08-03 21:58 ` Jeff Garzik
2003-08-05 19:28 ` Timothy Miller
2003-08-03 20:34 ` jamal
[not found] ` <3F2DBB2B.9050803@aarnet.edu.au>
2003-08-04 5:25 ` David S. Miller
2003-08-04 16:20 ` Web100 Matt Mathis
2003-08-06 7:12 ` TOE brain dump Andre Hedrick
[not found] ` <Pine.LNX.4.10.10308060009130.25045-100000@master.linux-ide .org>
2003-08-06 8:20 ` Lincoln Dale
2003-08-06 8:22 ` David S. Miller
2003-08-06 13:07 ` Jesse Pollard
2003-08-03 19:21 ` Eric W. Biederman
2003-08-04 19:24 ` Werner Almesberger
2003-08-04 19:26 ` David S. Miller
2003-08-05 17:25 ` Eric W. Biederman [this message]
2003-08-05 17:19 ` Eric W. Biederman
2003-08-06 5:13 ` Werner Almesberger
2003-08-06 7:58 ` Eric W. Biederman
2003-08-06 13:37 ` Werner Almesberger
2003-08-06 12:46 ` Jesse Pollard
2003-08-06 16:25 ` Andy Isaacson
2003-08-06 18:58 ` Jesse Pollard
2003-08-06 19:39 ` Andy Isaacson
2003-08-06 21:13 ` David Schwartz
2003-08-03 4:01 ` Ben Greear
2003-08-03 6:22 ` Alan Shih
2003-08-03 6:41 ` Jeff Garzik
2003-08-03 8:25 ` David Lang
2003-08-03 18:05 ` Werner Almesberger
2003-08-03 22:02 ` Alan Shih
2003-08-03 20:52 ` Alan Cox
2003-08-04 14:36 ` Ingo Oeser
2003-08-04 17:19 ` Alan Shih
2003-08-05 8:15 ` Ingo Oeser
2003-08-02 20:57 ` Alan Cox
2003-08-02 22:14 ` Werner Almesberger
2003-08-03 20:51 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-08-04 16:45 jamal
2003-08-04 18:48 ` Ihar 'Philips' Filipau
2003-08-04 19:42 ` jamal
2003-08-04 20:06 ` Ihar 'Philips' Filipau
2003-08-04 18:36 Perez-Gonzalez, Inaky
2003-08-04 19:03 ` Alan Cox
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=m1ptjkuica.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=davem@redhat.com \
--cc=werner@almesberger.net \
/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).