From: Jeff Sipek <jeffpc@optonline.net>
To: Jamie Lokier <jamie@shareable.org>
Cc: thockin@sun.com,
Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: sysconf - exposing constants to userspace
Date: Thu, 19 Feb 2004 19:29:45 -0500 [thread overview]
Message-ID: <200402191929.54604.jeffpc@optonline.net> (raw)
In-Reply-To: <20040220002034.GC5590@mail.shareable.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 19 February 2004 19:20, Jamie Lokier wrote:
> Jeff Sipek wrote:
> > I think that making something in /sys would make the most sense,
> > with one constant per file. We could dump the consts files to for
> > example /sys/consts, or make a logical directory structure to make
> > navigation easier.
>
> Isn't that very similar to the /proc/sys/kernel we have now?
If I understand the original post correctly, the numbers that we don't make
available to userspace are compile time constants. For example, since I can't
think of anything better, NR_CPUS. It is set during the config process, but
one cannot read the number from userspace while running that kernel. I know
that there are better examples, but I just can't think of any at the moment.
If I missed the point of the original post, please ignore me.
Jeff.
- --
Trust me, you don't want me doing _anything_ first thing in the morning.
- Linus Torvalds
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFANVUBwFP0+seVj/4RArdbAJ4tsq5cyDJ+058h1D6JDli1nsmP9ACeJnoN
pxE9BuRBNND271SGp81SMHM=
=rmLE
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-02-20 0:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 20:48 sysconf - exposing constants to userspace Tim Hockin
2004-02-19 21:30 ` Jeff Sipek
2004-02-20 0:20 ` Jamie Lokier
2004-02-20 0:21 ` Tim Hockin
2004-02-20 0:35 ` Chris Wright
2004-02-20 0:29 ` Jeff Sipek [this message]
2004-02-20 0:34 ` Tim Hockin
2004-02-20 0:52 ` Chris Wright
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=200402191929.54604.jeffpc@optonline.net \
--to=jeffpc@optonline.net \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@sun.com \
/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