netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Roland Dreier <roland@topspin.com>
Cc: alan@storlinksemi.com, linux-kernel@vger.kernel.org,
	linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: TCP IP Offloading Interface
Date: Sun, 13 Jul 2003 16:02:00 -0700	[thread overview]
Message-ID: <20030713160200.571716cf.davem@redhat.com> (raw)
In-Reply-To: <52u19qwg53.fsf@topspin.com>

On 13 Jul 2003 09:22:32 -0700
Roland Dreier <roland@topspin.com> wrote:

>     David> TOE is evil, read this:
> 
>     David> http://www.usenix.org/events/hotos03/tech/full_papers/mogul/mogul.pdf

> Your ideas are certainly very interesting, and I would be happy to see
> hardware that supports flow identification.  But the Usenix paper
> you're citing completely disagrees with you!

I didn't say I agree with all of Moguls ideas, just his anti-TOE
arguments.  For example, I also think RDMA sucks too yet he thinks
it's a good iea.

>  For example, Mogul writes:
> 
>  "Nevertheless, copy-avoidance designs have not been widely adopted,
>   due to significant limitations. For example, when network maximum
>   segment size (MSS) values are smaller than VM page sizes, which is
>   often the case, page-remapping techniques are insufficient (and
>   page-remapping often imposes overheads of its own.)"

On send this doesn't matter, on receive you use my clever receive
buffer handling + flow cache idea to accumulate the data portion of
packets into page sized chunks for the networking to flip.

You obviously don't understand my ideas if you think that it matters
whether there is some relationship between the MTU and the system
page size necessary for the scheme to work.

  parent reply	other threads:[~2003-07-13 23:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ODEIIOAOPGGCDIKEOPILCEMBCMAA.alan@storlinksemi.com>
2003-07-13  7:48 ` TCP IP Offloading Interface David S. Miller
2003-07-13 16:22   ` Roland Dreier
2003-07-13 16:31     ` Alan Cox
2003-07-13 16:49       ` Jeff Garzik
2003-07-13 16:58       ` Jeff Garzik
2003-07-13 23:02     ` David S. Miller [this message]
2003-07-13 23:35       ` Larry McVoy
2003-07-13 23:40         ` David S. Miller
2003-07-13 23:54           ` Larry McVoy
2003-07-13 23:53             ` David S. Miller
2003-07-14  0:22               ` Larry McVoy
2003-07-14  0:24                 ` David S. Miller
2003-07-14  0:48                   ` Larry McVoy
2003-07-14  0:46               ` Valdis.Kletnieks
2003-07-14  0:42                 ` David S. Miller
2003-07-16  2:46                   ` Matt Porter
2003-07-14  0:20       ` Roland Dreier
2003-07-14  0:28         ` David S. Miller
2003-07-16  2:37   ` Matt Porter
2003-07-15  5:42 Jordi Ros
2003-07-15  5:51 ` David S. Miller
2003-07-16  5:02   ` jamal
2003-07-16  1:51     ` Roland Dreier
2003-07-15 19:01 ` Ralph Doncaster
2003-07-15 19:36   ` Chris Dukes
  -- strict thread matches above, loose matches on Subject: below --
2003-07-15 16:28 David griego

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=20030713160200.571716cf.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=alan@storlinksemi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=roland@topspin.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;
as well as URLs for NNTP newsgroup(s).