From: Cacophonix <cacophonix@yahoo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
dean gaudet <dean-list-linux-kernel@arctic.org>
Cc: Ingo Molnar <mingo@elte.hu>, Rik van Riel <riel@conectiva.com.br>,
"David S. Miller" <davem@redhat.com>,
hch@caldera.de, netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: storage over IP (was Re: [PLEASE-TESTME] Zerocopy networking patch,
Date: Tue, 9 Jan 2001 20:18:15 -0800 (PST) [thread overview]
Message-ID: <20010110041815.23159.qmail@web121.yahoomail.com> (raw)
I haven't tracked the IP storage group too closely, but was at the San Diego IETF
where there were some interesting debates about this issue.
There is a write-up at http://ips.pdl.cs.cmu.edu/mail/msg02598.html
Now I'm not sure if I agree with some of the assumptions. And I share your concern
about using multiple tcp streams.
Thoughts?
cheers,
karthik
--- Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > <http://www.ietf.org/internet-drafts/draft-ietf-ips-fcovertcpip-01.txt>
> > show that both use TCP/IP. TCP/IP has variable length headers (or am i on
> > crack?), which totally complicates the receive path.
>
> TCP has variable length headers. It also prevents you re-ordering commands
> in the stream which would be beneficial. I've not checked if the draft uses
> multiple TCP streams but then you have scaling questions.
>
> Alan
>
__________________________________________________
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-10 4:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 4:18 Cacophonix [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-10 2:56 storage over IP (was Re: [PLEASE-TESTME] Zerocopy networking patch, 2.4.0-1) dean gaudet
2001-01-10 3:05 ` storage over IP (was Re: [PLEASE-TESTME] Zerocopy networking patch, Alan Cox
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=20010110041815.23159.qmail@web121.yahoomail.com \
--to=cacophonix@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=dean-list-linux-kernel@arctic.org \
--cc=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@oss.sgi.com \
--cc=riel@conectiva.com.br \
/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
all inboxes | Powered by JetHome®