linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@kernel.org>
To: Tony Ibbs <tibs@tonyibbs.co.uk>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Florian Fainelli <florian@openwrt.org>,
	Grant Likely <grant.likely@secretlab.ca>,
	Linux-embedded <linux-embedded@vger.kernel.org>,
	Tibs at Kynesim <tibs@kynesim.co.uk>,
	Richard Watts <rrw@kynesim.co.uk>
Subject: Re: RFC: [Restatement] KBUS messaging subsystem
Date: Mon, 15 Aug 2011 14:46:46 +0300	[thread overview]
Message-ID: <CAOJsxLEg-9hAQG99TkM+tqdTjZkpZwubOu1qM-6m7B5apZmh_w@mail.gmail.com> (raw)
In-Reply-To: <63D130AC-E6DF-4A61-BB69-30212D238F37@tonyibbs.co.uk>

Hi Tony,

On Sun, Aug 7, 2011 at 11:24 PM, Tony Ibbs <tibs@tonyibbs.co.uk> wrote:
> Real examples of usage that aren't the STB are a bit difficult to give
> because they belong to customer projects that we're not allowed to
> talk about.

That's part of the problem, I suppose. We usually don't merge new
kernel facilities unless we're able to understand (and see) real
applications that need them.

On Sun, Aug 7, 2011 at 11:24 PM, Tony Ibbs <tibs@tonyibbs.co.uk> wrote:
> I assume the real point of your post is that I wrote about the reasons
> why we made KBUS a kernel module, but did not really address the
> reasons why KBUS might want to be a kernel module in general usage.

I simply don't see a convincing argument why existing IPC and other
kernel mechanisms are not sufficient to implement what you need. I'm
sure there is one but it's not apparent from your emails.

The whole thing feels more like "lets put a message broker into the
kernel" rather than set of kernel APIs that make sense. I suppose the
rather extensive ioctl() ABI is partly to blame here.

I'm not saying you need to implement everything in userspace but I'm
also not convinced we want _all of this_ in the kernel.

                          Pekka

  reply	other threads:[~2011-08-15 11:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 17:21 [PATCH 00/11] RFC: KBUS messaging subsystem Tony Ibbs
2011-03-18 17:21 ` [PATCH 01/11] Documentation for KBUS Tony Ibbs
2011-03-18 17:21   ` [PATCH 02/11] KBUS external header file Tony Ibbs
2011-03-18 17:21     ` [PATCH 03/11] KBUS internal " Tony Ibbs
2011-03-18 17:21       ` [PATCH 04/11] KBUS main source file, basic device support only Tony Ibbs
2011-03-18 17:21         ` [PATCH 05/11] KBUS add support for messages Tony Ibbs
2011-03-18 17:21           ` [PATCH 06/11] KBUS add ability to receive messages only once Tony Ibbs
2011-03-18 17:21             ` [PATCH 07/11] KBUS add ability to add devices at runtime Tony Ibbs
2011-03-18 17:21               ` [PATCH 08/11] KBUS add Replier Bind Events Tony Ibbs
2011-03-18 17:21                 ` [PATCH 09/11] KBUS Replier Bind Event set-aside lists Tony Ibbs
2011-03-18 17:21                   ` [PATCH 10/11] KBUS report state to userspace Tony Ibbs
2011-03-18 17:21                     ` [PATCH 11/11] KBUS configuration and Makefile Tony Ibbs
2011-03-22 19:36 ` [PATCH 00/11] RFC: KBUS messaging subsystem Jonathan Corbet
2011-03-23 23:13   ` Tony Ibbs
2011-03-24 18:03     ` James Chapman
2011-03-27 19:07       ` Tony Ibbs
2011-04-15 21:34     ` [PATCH] extra/1 Allow setting the maximum KBUS message size Tony Ibbs
2011-04-15 22:46       ` Jonathan Corbet
2011-04-18 14:01         ` Mark Brown
2011-04-19 19:33           ` Tony Ibbs
2011-05-17  8:50   ` [PATCH 00/11] RFC: KBUS messaging subsystem Florian Fainelli
2011-05-22 19:58     ` Tony Ibbs
2011-07-06 16:15       ` Florian Fainelli
2011-07-28 21:48         ` RFC: [Restatement] " Tony Ibbs
2011-07-28 23:58           ` Colin Walters
2011-08-03 20:14             ` Tony Ibbs
2011-08-07 16:47               ` Tony Ibbs
2011-08-03 20:48           ` Pekka Enberg
2011-08-07 20:24             ` Tony Ibbs
2011-08-15 11:46               ` Pekka Enberg [this message]
2011-08-21 13:28                 ` Tony Ibbs
2011-08-22  1:15                   ` Bryan Donlan
2011-08-29  8:55                     ` Tony Ibbs
2011-08-03 20:23     ` [PATCH 00/11] RFC: " Tony Ibbs

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=CAOJsxLEg-9hAQG99TkM+tqdTjZkpZwubOu1qM-6m7B5apZmh_w@mail.gmail.com \
    --to=penberg@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=florian@openwrt.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rrw@kynesim.co.uk \
    --cc=tibs@kynesim.co.uk \
    --cc=tibs@tonyibbs.co.uk \
    /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).