From: Robin Holt <holt@sgi.com>
To: "Ragnar Kjørstad" <kernel@ragnark.vestdata.no>
Cc: Tim Schmielau <tim@physik3.uni-rostock.de>,
lkml <linux-kernel@vger.kernel.org>,
Arthur Corliss <corliss@digitalmages.com>,
Albert Cahalan <albert@users.sourceforge.net>
Subject: Re: [patch,rfc] BSD accounting format rework
Date: Fri, 19 Mar 2004 15:14:57 -0600 [thread overview]
Message-ID: <20040319211457.GA19662@lnx-holt> (raw)
In-Reply-To: <20040319191916.GQ1066@vestdata.no>
> One idea is to add the size of the structure to log. The start of the
> struct could be something like:
> struct acct_base {
> char flags;
> char ac_version;
> __u16 ac_size;
> }
>
> This makes future extentions easier in two seperate ways:
> Userspace acct can recognize futuristic data structures. It will, of
> course, not be able to process them, but it can warn the user and then
> continue on to the next struct.
>
> Also, it would make it possible to add new fields at the end of the
> structure _without_ bumping the version-number. (Like an extention to
> the same format). When userspace find a v2 struct bigger that it's
> "struct acct_v2" it can parse the first part of the data with struct
> acct_v2 and just ignore the rest. This makes it trivial to add new
> fields without breaking userspace.
How about breaking the ac_version structure down as two nibbles? One
half being the major version and the other half being a minor version.
The major version, when changed, means the structure is no longer compatible.
The minor version can be changed when existing fields are not modified
in either form or function.
Robin
next prev parent reply other threads:[~2004-03-19 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 13:47 [PATCH] fix HZ leaking to userspace in BSD accounting Tim Schmielau
2004-03-19 14:09 ` [patch,rfc] BSD accounting format rework Tim Schmielau
2004-03-19 19:19 ` Ragnar Kjørstad
2004-03-19 21:14 ` Robin Holt [this message]
2004-03-21 1:28 ` Tim Schmielau
2004-03-21 1:21 ` Tim Schmielau
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=20040319211457.GA19662@lnx-holt \
--to=holt@sgi.com \
--cc=albert@users.sourceforge.net \
--cc=corliss@digitalmages.com \
--cc=kernel@ragnark.vestdata.no \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@physik3.uni-rostock.de \
/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
all inboxes | Powered by JetHome®