From: David Howells <dhowells@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: dhowells@redhat.com,
Linus Torvalds <torvalds@linux-foundation.org>,
YueHaibing <yuehaibing@huawei.com>,
Marc Dionne <marc.dionne@auristor.com>,
linux-afs@lists.infradead.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL afs: Development for 5.4
Date: Thu, 19 Sep 2019 15:24:00 +0100 [thread overview]
Message-ID: <8821.1568903040@warthog.procyon.org.uk> (raw)
In-Reply-To: <20190919131537.GA15392@bombadil.infradead.org>
Matthew Wilcox <willy@infradead.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
next prev parent reply other threads:[~2019-09-19 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 11:09 [GIT PULL afs: Development for 5.4 David Howells
2019-09-19 0:22 ` Linus Torvalds
2019-09-19 0:24 ` Linus Torvalds
2019-09-19 1:55 ` pr-tracker-bot
2019-09-19 6:40 ` David Howells
2019-09-19 9:49 ` David Howells
2019-09-19 13:15 ` Matthew Wilcox
2019-09-19 14:03 ` Ilya Dryomov
2019-09-19 15:05 ` Jeffrey E Altman
2019-09-19 14:24 ` David Howells [this message]
2019-09-19 16:29 ` Linus Torvalds
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=8821.1568903040@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
--cc=yuehaibing@huawei.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).