From: Albert Cahalan <albert@users.sf.net>
To: Tim Schmielau <tim@physik3.uni-rostock.de>
Cc: Albert Cahalan <albert@users.sourceforge.net>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>,
corliss@digitalmages.com, riel@redhat.com, jerj@coplanar.net
Subject: Re: [PATCH] 2.6.x BSD Process Accounting w/High UID
Date: 10 Mar 2004 17:09:16 -0500 [thread overview]
Message-ID: <1078956556.2233.586.camel@cube> (raw)
In-Reply-To: <Pine.LNX.4.53.0403101844140.15085@gockel.physik3.uni-rostock.de>
On Wed, 2004-03-10 at 12:47, Tim Schmielau wrote:
> On Wed, 10 Mar 2004, Albert Cahalan wrote:
>
> > That's a 42-bit number instead of a 36-bit one.
>
> OK, your format clearly wins. Especially since I think that comp_t can
> only encode a 34-bit number.
That is correct. 42 - 8 != 36
My diagram was right; the math was not.
> But I favor your suggestion of 32-bit IEEE floats even more,
> as it doesn't need a change to the GNU acct tools.
I'm surprised. Do the tools rely on a #define for this?
Is there a reason to have the whole struct be a
power of two? If so, and you don't wish to expand
it to 128 bytes, consider packing 3 80-byte records
and a 16-byte header into 256 bytes.
next prev parent reply other threads:[~2004-03-10 22:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 1:59 [PATCH] 2.6.x BSD Process Accounting w/High UID Albert Cahalan
2004-03-10 9:08 ` Tim Schmielau
2004-03-10 16:41 ` Albert Cahalan
2004-03-10 17:28 ` Tim Schmielau
2004-03-10 17:47 ` Tim Schmielau
2004-03-10 22:09 ` Albert Cahalan [this message]
2004-03-11 0:55 ` Tim Schmielau
-- strict thread matches above, loose matches on Subject: below --
2004-03-04 18:04 Arthur Corliss
2004-03-04 19:51 ` Rik van Riel
2004-03-04 20:39 ` Arthur Corliss
2004-03-04 21:54 ` Tim Schmielau
2004-03-04 22:33 ` Arthur Corliss
2004-03-09 16:16 ` Jeremy Jackson
2004-03-09 18:22 ` 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=1078956556.2233.586.camel@cube \
--to=albert@users.sf.net \
--cc=albert@users.sourceforge.net \
--cc=corliss@digitalmages.com \
--cc=jerj@coplanar.net \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--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