All of lore.kernel.org
 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 17:28:36 -0700	[thread overview]
Message-ID: <20030713172836.5dd493f5.davem@redhat.com> (raw)
In-Reply-To: <52llv2vu06.fsf@topspin.com>

On 13 Jul 2003 17:20:41 -0700
Roland Dreier <roland@topspin.com> wrote:

>     David> I didn't say I agree with all of Moguls ideas, just his
>     David> anti-TOE arguments.  For example, I also think RDMA sucks
>     David> too yet he thinks it's a good iea.
> 
> Sure, he talks about some weaknesses of TOE, but his conclusion is
> that the time has come for OS developers to start working on TCP
> offload (for storage).

The bad assumption here is that this belongs in the OS.

Let me ask you this, how many modern scsi drivers have to speak every
piece of the SCSI bus protocol.  Or fibre channel?  All of it is
done on the cards, and that is what I think the iSCSI people should
be doing instead of putting garbage into the OS.

And I've presented a solution to the problem at the OS level that
doesn't require broken things like TOE and RDMA yet arrives at
the same solution.

> But I also think Mogul is right: iSCSI HBAs are going to force OS
> designers to deal with TCP offload.

You don't need to offload TCP, it's the segmentation and checksuming
that has the high cost not the actual TCP logic in the operating
system.

RDMA and TOE both add unnecessary complications.  My solution requires
no protocol changes, just smart hardware which needs to be designed
for any of the presented ideas anyways.


  reply	other threads:[~2003-07-14  0:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-13  7:33 TCP IP Offloading Interface Alan Shih
2003-07-13  7:48 ` 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
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 [this message]
2003-07-16  2:37   ` Matt Porter
2003-07-13 14:51 ` Jeff Garzik
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
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=20030713172836.5dd493f5.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.