From: Tony Ibbs <tibs@kynesim.co.uk>
To: Linux-embedded <linux-embedded@vger.kernel.org>
Cc: Grant Likely <grant.likely@secretlab.com>,
Tibs at home <tibs@tonyibbs.co.uk>,
Richard Watts <rrw@kynesim.co.uk>
Subject: [RFC][PATCH] KBUS messaging subsystem
Date: Fri, 28 Jan 2011 17:50:40 +0000 [thread overview]
Message-ID: <20110128175040.72cf332a@spoon> (raw)
KBUS is a lightweight Linux-kernel mediated message system,
particularly intended for use in embedded environments.
It is meant to be simple to use and understand. It is particularly
designed to provide predictable message delivery, deterministic
message ordering, and a guaranteed reply for each request.
We have various customers using KBUS in real life, and believe it to
be useful. I had a showcase table for KBUS at the ELCE in Cambridge,
October last year, and there seemed to be interest.
We'd like some advice on how to submit this - I assume that submitting
patches to the Embedded Linux mailing list first would be sensible,
since we believe this to be an area that will find KBUS interesting.
The KBUS project home page is at http://kbus-messaging.org/
The KBUS specification can be found at
http://html.kbus.googlecode.com/hg/docs/html/specification.html
Userland support, plus unit tests for the kernel module, are in the
Google code repositories. There's a GettingStarted page linked from
the KBUS home page.
We've got a working repository with Linux 2.6.37 patched for KBUS,
available via:
git pull git://github.com/crazyscot/linux-2.6-kbus.git kbus-2.6.37
Our tentative patch is at
http://kbus.googlecode.com/files/0001-KBUS-messaging-subsystem.patch
The diffstat for the patch is:
Documentation/Kbus.txt | 1189 ++++++++++
include/linux/kbus_defns.h | 666 ++++++
init/Kconfig | 3 +
ipc/Kconfig | 99 +
ipc/Makefile | 1 +
ipc/kbus.c | 5120 ++++++++++++++++++++++++++++++++++++++++++++
ipc/kbus_internal.h | 773 +++++++
7 files changed, 7851 insertions(+), 0 deletions(-)
Should I just submit the patch to this list?
Tibs
next reply other threads:[~2011-01-28 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 17:50 Tony Ibbs [this message]
2011-01-28 19:20 ` [RFC][PATCH] KBUS messaging subsystem Sam Ravnborg
2011-02-03 16:59 ` Tony Ibbs
[not found] <20110128180158.6f670a51@spoon>
2011-02-02 3:40 ` Grant Likely
2011-02-03 17:04 ` Tony Ibbs
2011-02-03 17:32 ` Grant Likely
2011-02-06 21:07 ` 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=20110128175040.72cf332a@spoon \
--to=tibs@kynesim.co.uk \
--cc=grant.likely@secretlab.com \
--cc=linux-embedded@vger.kernel.org \
--cc=rrw@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 read-only IMAP folder(s) and NNTP newsgroup(s).