[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8821.1568903040@warthog.procyon.org.uk>
Date: Thu, 19 Sep 2019 15:24:00 +0100
From: David Howells <dhowells@...hat.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: dhowells@...hat.com,
Linus Torvalds <torvalds@...ux-foundation.org>,
YueHaibing <yuehaibing@...wei.com>,
Marc Dionne <marc.dionne@...istor.com>,
linux-afs@...ts.infradead.org,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL afs: Development for 5.4
Matthew Wilcox <willy@...radead.org> wrote:
> Why is it organised this way? I mean, yes, technically, rxrpc is a
> generic layer-6 protocol that any blah blah blah, but in practice no
> other user has come up in the last 37 years, so why bother pretending
> one is going to? Just git mv net/rxrpc fs/afs/ and merge everything
> through your tree.
Note that, unlike 9p, sunrpc and ceph, rxrpc is exposed as a network protocol
and can be used directly with socket(AF_RXRPC, ...). I have part of a
userspace tool suite that uses this.
David
Powered by blists - more mailing lists