From: Tony Ibbs <tibs@tonyibbs.co.uk>
To: Linux-embedded <linux-embedded@vger.kernel.org>
Cc: Tibs at Kynesim <tibs@kynesim.co.uk>,
Richard Watts <rrw@kynesim.co.uk>,
Grant Likely <grant.likely@secretlab.ca>
Subject: [PATCH 0/5] RFC: KBUS messaging subsystem
Date: Sun, 27 Feb 2011 18:11:43 +0000 [thread overview]
Message-ID: <cover.1298829754.git.tibs@tonyibbs.co.uk> (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 designed to
provide predictable message delivery, deterministic message ordering,
and a guaranteed reply for each request.
It is especially aimed at situations where existing solutions,
such as DBUS, cannot be used, typically because of system constraints.
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.
I am hoping to get a response from this list before attempting to send
to the kernel list, since I believe this list should contain people
who might be most interested in using it.
The KBUS project home page is at http://kbus-messaging.org/, from
which there are various useful links.
There is 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
This is a resubmission of the original RFC to the Linux-Embedded list,
having:
a) changed to use __u32 instead of uint32_t and
b) changed to use kernel messaging mechanisms (also removing
some messaging that should not be needed). These in response
to the suggestion of Sam Ravnborg
c) split into multiple in-line patches, as is normal practice,
and as requested by Grant Likely
Tibs (5):
Documentation for KBUS
External header file for KBUS
Kconfig files and Makefile for KBUS
Internal header file for KBUS
KBUS itself, the main source file
Documentation/Kbus.txt | 1222 +++++++++++
include/linux/kbus_defns.h | 666 ++++++
init/Kconfig | 3 +
ipc/Kconfig | 99 +
ipc/Makefile | 5 +
ipc/kbus.c | 4927 ++++++++++++++++++++++++++++++++++++++++++++
ipc/kbus_internal.h | 709 +++++++
7 files changed, 7631 insertions(+), 0 deletions(-)
create mode 100644 Documentation/Kbus.txt
create mode 100644 include/linux/kbus_defns.h
create mode 100644 ipc/Kconfig
create mode 100644 ipc/kbus.c
create mode 100644 ipc/kbus_internal.h
next reply other threads:[~2011-02-27 18:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-27 18:11 Tony Ibbs [this message]
2011-02-27 18:11 ` [PATCH 1/5] Documentation for KBUS Tony Ibbs
2011-02-27 18:11 ` [PATCH 2/5] External header file " Tony Ibbs
2011-02-27 18:11 ` [PATCH 3/5] Kconfig files and Makefile " Tony Ibbs
2011-02-27 18:11 ` [PATCH 4/5] Internal header file " Tony Ibbs
2011-02-27 18:19 ` [PATCH 3/5] Kconfig files and Makefile " Randy Dunlap
2011-02-27 19:36 ` Tony Ibbs
2011-02-27 19:26 ` [PATCH 5/5] KBUS source file Tony Ibbs
2011-02-27 20:25 ` Randy Dunlap
2011-02-28 19:23 ` Sam Ravnborg
2011-02-28 22:25 ` Tony Ibbs
2011-03-01 5:42 ` Sam Ravnborg
2011-02-28 7:48 ` [PATCH 0/5] RFC: KBUS messaging subsystem Grant Likely
2011-02-28 7:52 ` Grant Likely
2011-02-28 19:13 ` 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=cover.1298829754.git.tibs@tonyibbs.co.uk \
--to=tibs@tonyibbs.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=linux-embedded@vger.kernel.org \
--cc=rrw@kynesim.co.uk \
--cc=tibs@kynesim.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).