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 17:10:08 -0400 [thread overview]
Message-ID: <44A2F030.4080102@pobox.com> (raw)
In-Reply-To: <54AD0F12E08D1541B826BE97C98F99F15F5B6D@NT-SJCA-0751.brcm.ad.broadcom.com>
Caitlin Bestler wrote:
> netdev-owner@vger.kernel.org wrote:
>> From: Steve Wise <swise@opengridcomputing.com>
>> Date: Wed, 28 Jun 2006 09:54:57 -0500
>>
>>> Doesn't iSCSI have this same issue?
>> Software iSCSI implementations don't have the issue because
>> they go through the stack using normal sockets and normal
>> device send and receive.
>
> But hardware iSCSI implementations, which already exist,
> do not work through normal sockets.
No, they work through normal SCSI stack...
Jeff
next prev parent reply other threads:[~2006-06-28 21:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 18:49 TOE, etc Caitlin Bestler
2006-06-28 21:10 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-28 23:54 Caitlin Bestler
2006-06-28 21:15 Caitlin Bestler
2006-06-28 23:43 ` Jeff Garzik
2006-06-29 14:09 ` Steve Wise
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=44A2F030.4080102@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).