From: Matthew Wilcox <matthew@wil.cx>
To: Marcel Holtmann <holtmann@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>, Greg KH <greg@kroah.com>,
bgmerrell@novell.com, hirofuchi@users.sourceforge.net,
linux-kernel@vger.kernel.org, usbip-devel@lists.sourceforge.net
Subject: Re: USBIP protocol
Date: Fri, 29 Aug 2008 14:46:27 -0600 [thread overview]
Message-ID: <20080829204627.GB1239@parisc-linux.org> (raw)
In-Reply-To: <1220049103.7145.23.camel@californication>
On Sat, Aug 30, 2008 at 12:31:43AM +0200, Marcel Holtmann wrote:
> Hi Matthew,
>
> > > I'm in the middle of implementing a userspace client for usbip and I
> > > strongly feel that the protocol needs to be changed before it is merged.
> > >
> > > - I'm unconvinced that TCP is the correct protocol to be running this over.
> > > I understand the reluctance to use UDP, but the protocol is fundamentally
> > > packet-based. If TCP is used, the delimitation of packets within the
> > > stream needs to be much more robust.
> >
> > If you want reliable transport with record boundaries an alternative
> > would be also SCTP. Main drawback is that firewalls often don't support it
> > though (but presumably that wouldn't be a big issue for this)
>
> I would also have proposed SCTP. The telco carries seems be very happy
> with it.
I'm actually looking into the sunrpc protocol. That has the advantages:
- Already has an in-kernel implementation
- Widely understood and properly documented
- Can be run over TCP or UDP or even RDMA
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-08-29 20:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 14:02 Matthew Wilcox
2008-08-29 14:06 ` Andi Kleen
2008-08-29 22:31 ` Marcel Holtmann
2008-08-29 20:46 ` Matthew Wilcox [this message]
2008-08-29 20:51 ` Willy Tarreau
2008-08-29 14:30 ` Greg KH
2008-08-29 14:43 ` Matthew Wilcox
2008-08-29 14:54 ` Greg KH
2008-08-29 15:36 ` Matthew Wilcox
2008-08-29 15:53 ` Dave Higton
2008-09-03 4:25 ` Matthew Wilcox
2008-09-03 15:40 ` Alan Stern
2008-09-03 19:10 ` Matthew Wilcox
2008-09-03 20:15 ` Alan Stern
2008-09-04 21:48 ` Matthew Wilcox
2008-09-04 22:15 ` Greg KH
2008-09-05 3:26 ` Pete Zaitcev
2008-09-05 11:37 ` Tilman Schmidt
2008-09-05 15:05 ` Alan Stern
2008-09-09 0:53 ` Matthew Wilcox
2008-09-09 7:12 ` Steve Calfee
2008-09-09 7:33 ` Greg KH
2008-09-09 8:04 ` Greg KH
2008-09-09 15:21 ` Alan Stern
2008-09-03 15:57 ` Greg KH
2008-09-03 19:43 ` Matthew Wilcox
2008-09-04 2:41 ` Greg KH
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=20080829204627.GB1239@parisc-linux.org \
--to=matthew@wil.cx \
--cc=andi@firstfloor.org \
--cc=bgmerrell@novell.com \
--cc=greg@kroah.com \
--cc=hirofuchi@users.sourceforge.net \
--cc=holtmann@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=usbip-devel@lists.sourceforge.net \
/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
Powered by JetHome