netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Caitlin Bestler <caitlinb@broadcom.com>
Cc: David Miller <davem@davemloft.net>,
	swise@opengridcomputing.com, herbert@gondor.apana.org.au,
	netdev@vger.kernel.org
Subject: Re: TOE, etc.
Date: Wed, 28 Jun 2006 19:43:06 -0400	[thread overview]
Message-ID: <44A3140A.1040901@pobox.com> (raw)
In-Reply-To: <54AD0F12E08D1541B826BE97C98F99F15F5BA4@NT-SJCA-0751.brcm.ad.broadcom.com>

Caitlin Bestler wrote:
> Jeff Garzik wrote:
>> Caitlin Bestler wrote:
>>> But hardware iSCSI implementations, which already exist, do not work
>>> through normal sockets.

>> No, they work through normal SCSI stack...

> Correct.
> 
> But they then interface to the network using none of the network stack.
> The normal SCSI stack does not control that it any way.

Correct.  And the network stack is completely unaware of whatever IP 
addresses, ARP tables, routing tables, etc. it is using.


> NFS over RDMA is part of the file system. That doesn't change the fact
> that it's use of IP Addresses needs to be co-ordinated with the network
> stack, and indeed that address based authentication *assumes* that this
> is the case. (and yes, there are preferable means of authentication, but
> authenticating based on IP address is already supported).

Sounds quite broken to me.


> But back on the main point, if implementing SCSI services over a
> TCP connection is acceptable even though it does not use a kernel
> socket, why would it not be acceptable to implement RDMA services
> over a TCP connection without using a kernel socket?

Because SCSI doesn't force nasty hooks into the net stack to allow for 
sharing of resources with a proprietary black box of unknown quality.

	Jeff



  reply	other threads:[~2006-06-28 23:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 21:15 TOE, etc Caitlin Bestler
2006-06-28 23:43 ` Jeff Garzik [this message]
2006-06-29 14:09   ` Steve Wise
  -- strict thread matches above, loose matches on Subject: below --
2006-06-28 23:54 Caitlin Bestler
2006-06-28 18:49 Caitlin Bestler
2006-06-28 21:10 ` Jeff Garzik
2006-06-28 16:25 Caitlin Bestler
2006-06-28  3:37 [PATCH Round 3 0/2][RFC] Network Event Notifier Mechanism Herbert Xu
2006-06-28  4:18 ` TOE, etc. (was Re: [PATCH Round 3 0/2][RFC] Network Event Notifier Mechanism) Jeff Garzik
2006-06-28  4:29   ` Herbert Xu
2006-06-28  4:43     ` TOE, etc David Miller
2006-06-28  5:35       ` Herbert Xu
2006-06-28  6:31         ` David Miller
2006-06-28 14:41         ` Steve Wise
2006-06-28 14:54         ` Steve Wise
2006-06-28 18:36           ` David Miller
2006-06-28 18:56             ` Steve Wise

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=44A3140A.1040901@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=caitlinb@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=swise@opengridcomputing.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).