From: David Miller <davem@davemloft.net>
To: swise@opengridcomputing.com
Cc: herbert@gondor.apana.org.au, jgarzik@pobox.com, netdev@vger.kernel.org
Subject: Re: TOE, etc.
Date: Wed, 28 Jun 2006 11:36:46 -0700 (PDT) [thread overview]
Message-ID: <20060628.113646.85408870.davem@davemloft.net> (raw)
In-Reply-To: <1151506497.14895.51.camel@stevo-desktop>
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.
next prev parent reply other threads:[~2006-06-28 18:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 20:50 [PATCH Round 3 0/2][RFC] Network Event Notifier Mechanism Steve Wise
2006-06-27 20:51 ` [PATCH Round 3 1/2] " Steve Wise
2006-06-27 20:51 ` [PATCH Round 3 2/2] Core network changes to support network event notification Steve Wise
2006-06-28 2:54 ` [PATCH Round 3 0/2][RFC] Network Event Notifier Mechanism Herbert Xu
2006-06-28 3:04 ` Herbert Xu
2006-06-28 3:24 ` Jeff Garzik
2006-06-28 3:37 ` 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:40 ` Jeff Garzik
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 [this message]
2006-06-28 18:56 ` Steve Wise
2006-06-28 14:31 ` TOE, etc. (was Re: [PATCH Round 3 0/2][RFC] Network Event Notifier Mechanism) Steve Wise
2006-06-28 14:18 ` Steve Wise
-- strict thread matches above, loose matches on Subject: below --
2006-06-28 16:25 TOE, etc Caitlin Bestler
2006-06-28 18:49 Caitlin Bestler
2006-06-28 21:10 ` Jeff Garzik
2006-06-28 21:15 Caitlin Bestler
2006-06-28 23:43 ` Jeff Garzik
2006-06-29 14:09 ` Steve Wise
2006-06-28 23:54 Caitlin Bestler
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=20060628.113646.85408870.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jgarzik@pobox.com \
--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).