From: Steve Wise <swise@opengridcomputing.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Caitlin Bestler <caitlinb@broadcom.com>,
David Miller <davem@davemloft.net>,
herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: TOE, etc.
Date: Thu, 29 Jun 2006 09:09:11 -0500 [thread overview]
Message-ID: <1151590151.6424.10.camel@stevo-desktop> (raw)
In-Reply-To: <44A3140A.1040901@pobox.com>
>
> > 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
>
The netevent notifier patch in question seemed to be reasonable hooks
for notifying kernel and user mode modules of certain network events.
In fact, it went through 3 review cycles and was improved by feedback
from Dave and others. eg: It was integrated with netlink to provide
user mode notifications.
Then someone says 'TOE' and suddenly the hooks are nasty?
Steve.
next prev parent reply other threads:[~2006-06-29 14:09 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
2006-06-29 14:09 ` Steve Wise [this message]
-- 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=1151590151.6424.10.camel@stevo-desktop \
--to=swise@opengridcomputing.com \
--cc=caitlinb@broadcom.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
/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).