From: Arnd Bergmann <arnd@arndb.de>
To: Tom Gundersen <teg@jklm.no>
Cc: Andy Lutomirski <luto@amacapital.net>,
David Herrmann <dh.herrmann@gmail.com>,
Hannes Reinecke <hare@suse.com>, Jiri Kosina <jikos@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Josh Triplett <josh@joshtriplett.org>, Greg KH <greg@kroah.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC v1 02/14] bus1: provide stub cdev /dev/bus1
Date: Sun, 30 Oct 2016 00:13:14 +0200 [thread overview]
Message-ID: <201610300013.14598.arnd@arndb.de> (raw)
In-Reply-To: <CAG-2HqXSGac7PXuHfG0Osh1LN_recr6knPYbCcY12Ks5GBDeYw@mail.gmail.com>
On Thursday 27 October 2016, Tom Gundersen wrote:
> On Thu, Oct 27, 2016 at 11:11 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Thursday, October 27, 2016 1:54:05 AM CEST Tom Gundersen wrote:
> >> On Thu, Oct 27, 2016 at 1:19 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> >> > This may have been covered elsewhere, but could this use syscalls instead?
> >>
> >> Yes, syscalls would work essentially the same. For now, we are using a
> >> cdev as it makes it a lot more convenient to develop and test as an
> >> out-of-tree module, but that could be changed easily before the final
> >> submission, if that's what we want.
> >
> >
> > Generally speaking, I think syscalls would be appropriate here, and put
> > bus1 into a similar category as the other ipc interfaces (shm, msg, sem,
> > mqueue, ...).
>
> Could you elaborate on why you think syscalls would be more
> appropriate than ioctls?
Linus already answered this, but I'd also add that core kernel
features just make sense to be syscalls, rather than stuffing
them in a random device driver.
> > - Have a mountable file system, and use open() on that to create
> > connections. Advantages are that it's fairly easy to have one
> > instance per fs-namespace, and you can have user-defined naming
> > of objects in the file system.
>
> Note that currently we only have one object (/dev/bus1) and each fd is
> disconnected from anything else on creation, so not sure what benefits
> a filesystem (or several instances of it) would give?
I have not tried to understand some of the main concepts of bus1,
so I simply assumed that there was some way of looking up handles
of other instances. Using a file system gives you a natural way
to look up resources by name the way we do e.g. for mq_open(),
and it lets you easy decide whether containers should share
a view of the same namespace by mounting the same instance of
the file system into them or having separate instances.
If you don't ever need to look up a handle by name in bus1, using
a mountable file system would not help you.
Arnd
next prev parent reply other threads:[~2016-10-29 22:13 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 19:17 [RFC v1 00/14] Bus1 Kernel Message Bus David Herrmann
2016-10-26 19:17 ` [RFC v1 01/14] bus1: add bus1(7) man-page David Herrmann
2016-10-27 23:12 ` Kirill A. Shutemov
2016-10-26 19:17 ` [RFC v1 02/14] bus1: provide stub cdev /dev/bus1 David Herrmann
2016-10-26 23:19 ` Andy Lutomirski
2016-10-26 23:54 ` Tom Gundersen
2016-10-27 9:11 ` Arnd Bergmann
2016-10-27 15:25 ` Tom Gundersen
2016-10-27 16:37 ` Linus Torvalds
2016-10-27 16:39 ` Tom Gundersen
2016-10-29 22:13 ` Arnd Bergmann [this message]
2016-10-26 19:17 ` [RFC v1 03/14] bus1: util - active reference utility library David Herrmann
2016-10-26 19:18 ` [RFC v1 04/14] bus1: util - fixed list " David Herrmann
2016-10-27 12:37 ` Peter Zijlstra
2016-10-27 12:48 ` David Herrmann
2016-10-27 12:56 ` Arnd Bergmann
2016-10-27 13:31 ` David Herrmann
2016-10-26 19:18 ` [RFC v1 05/14] bus1: util - pool " David Herrmann
2016-10-27 12:54 ` Peter Zijlstra
2016-10-27 12:59 ` Peter Zijlstra
2016-10-27 15:00 ` Peter Zijlstra
2016-10-27 15:14 ` Peter Zijlstra
2016-10-26 19:18 ` [RFC v1 06/14] bus1: util - queue " David Herrmann
2016-10-27 15:27 ` Peter Zijlstra
2016-10-27 16:43 ` Peter Zijlstra
2016-10-28 11:33 ` Tom Gundersen
2016-10-28 13:33 ` Peter Zijlstra
2016-10-28 13:47 ` Tom Gundersen
2016-10-28 13:58 ` Peter Zijlstra
2016-10-28 14:33 ` Tom Gundersen
2016-10-28 16:49 ` Peter Zijlstra
2016-10-26 19:18 ` [RFC v1 07/14] bus1: tracking user contexts David Herrmann
2016-10-26 19:18 ` [RFC v1 08/14] bus1: implement peer management context David Herrmann
2016-10-28 12:06 ` Richard Weinberger
2016-10-28 13:18 ` Tom Gundersen
2016-10-28 13:21 ` Richard Weinberger
2016-10-28 13:05 ` Richard Weinberger
2016-10-28 13:23 ` Tom Gundersen
2016-10-28 13:54 ` Richard Weinberger
2016-10-26 19:18 ` [RFC v1 09/14] bus1: provide transaction context for multicasts David Herrmann
2016-10-28 14:37 ` Peter Zijlstra
2016-10-26 19:18 ` [RFC v1 10/14] bus1: add handle management David Herrmann
2016-10-26 19:18 ` [RFC v1 11/14] bus1: implement message transmission David Herrmann
2016-10-26 19:18 ` [RFC v1 12/14] bus1: hook up file-operations David Herrmann
2016-10-26 19:18 ` [RFC v1 13/14] bus1: limit and protect resources David Herrmann
2016-10-26 19:18 ` [RFC v1 14/14] bus1: basic user-space kselftests David Herrmann
2016-10-26 19:39 ` [RFC v1 00/14] Bus1 Kernel Message Bus Linus Torvalds
2016-10-26 20:34 ` David Herrmann
2016-10-27 0:45 ` Kirill A. Shutemov
2016-10-29 21:04 ` Josh Triplett
2016-11-02 14:45 ` David Herrmann
2017-01-30 22:11 ` Pavel Machek
2016-10-27 11:10 ` Michael Kerrisk
2016-10-28 13:11 ` Richard Weinberger
2016-10-28 13:37 ` Tom Gundersen
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=201610300013.14598.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=dh.herrmann@gmail.com \
--cc=greg@kroah.com \
--cc=hare@suse.com \
--cc=jikos@kernel.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=rostedt@goodmis.org \
--cc=teg@jklm.no \
--cc=torvalds@linux-foundation.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
Powered by JetHome