From: Willy Tarreau <willy@w.ods.org>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Ahmad Reza Cheraghi <a_r_cheraghi@yahoo.com>,
linux-kernel@vger.kernel.org
Subject: Re: Why no XML in the Kernel?
Date: Sun, 2 Oct 2005 15:47:02 +0200 [thread overview]
Message-ID: <20051002134702.GA22601@alpha.home.local> (raw)
In-Reply-To: <433FBE59.8000806@superbug.co.uk>
On Sun, Oct 02, 2005 at 12:02:49PM +0100, James Courtier-Dutton wrote:
> Nick Piggin wrote:
>
> >Ahmad Reza Cheraghi wrote:
> >
> >>Can somebody tell me why the Kernel-Development dont
> >>wanne have XML is being used in the Kernel??
> >>
> >
> >Because nobody has come up with a good reason why it
> >should be. Same as anything that isn't in the kernel.
> >
> >Nick
> >
> I have a requirement to pass information from the kernel to user space.
> The information is passed fairly rarely, but over time extra parameters
> are added. At the moment we just use a struct, but that means that the
> kernel and the userspace app have to both keep in step. If something
> like XML was used, we could implement new parameters in the kernel, and
> the user space could just ignore them, until the user space is upgraded.
> XML would initially seem a good idea for this, but are there any methods
> currently used in the kernel that could handle these parameter changes
> over time.
Yes, look at /proc/meminfo for instance. Everytime you need to return
multiple values from a single file, you can easily do it with one key
per line using the following syntax :
key: value [value ...]
It's also how SMTP and HTTP works and servers often send data that most
clients simply ignore.
Regards,
Willy
next prev parent reply other threads:[~2005-10-02 13:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-02 9:41 Why no XML in the Kernel? Ahmad Reza Cheraghi
2005-10-02 9:50 ` Nick Piggin
2005-10-02 11:02 ` James Courtier-Dutton
2005-10-02 10:37 ` Nick Piggin
2005-10-02 11:57 ` Bas Westerbaan
2005-10-02 11:09 ` James Bruce
2005-10-02 13:47 ` Willy Tarreau [this message]
2005-10-03 19:21 ` Bill Davidsen
2005-10-02 18:53 ` Jon Masters
2005-10-03 15:08 ` Nix
2005-10-03 15:35 ` Al Viro
2005-10-03 19:47 ` Nix
2005-10-03 19:56 ` linux-os (Dick Johnson)
2005-10-05 21:11 ` Dave Airlie
2005-10-05 21:31 ` Nix
2005-10-05 22:57 ` Dave Airlie
2005-10-05 23:07 ` Nix
2005-10-05 23:36 ` Dave Airlie
2005-10-05 22:22 ` jmerkey
2005-10-05 23:46 ` Dave Airlie
2005-10-07 22:14 ` Matan Ziv-Av
2005-10-02 21:55 ` Martin J. Bligh
2005-10-03 4:45 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2005-10-08 1:34 Luke Kenneth Casson Leighton
2005-10-09 15:38 ` Horst von Brand
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=20051002134702.GA22601@alpha.home.local \
--to=willy@w.ods.org \
--cc=James@superbug.co.uk \
--cc=a_r_cheraghi@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.