All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Hockin <thockin@sun.com>
To: Jeff Sipek <jeffpc@optonline.net>
Cc: Jamie Lokier <jamie@shareable.org>,
	Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: sysconf - exposing constants to userspace
Date: Thu, 19 Feb 2004 16:34:55 -0800	[thread overview]
Message-ID: <20040220003455.GI9155@sun.com> (raw)
In-Reply-To: <200402191929.54604.jeffpc@optonline.net>

On Thu, Feb 19, 2004 at 07:29:45PM -0500, Jeff Sipek wrote:
> 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.

No, you got it.  BUt I was specifically thinking of POSIX sysconf stuff,
like NGROUPS_MAX.  See <linux/limits.h>.

-- 
Tim Hockin
Sun Microsystems, Linux Software Engineering
thockin@sun.com
All opinions are my own, not Sun's

  reply	other threads:[~2004-02-20  0:48 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
2004-02-20  0:34       ` Tim Hockin [this message]
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=20040220003455.GI9155@sun.com \
    --to=thockin@sun.com \
    --cc=jamie@shareable.org \
    --cc=jeffpc@optonline.net \
    --cc=linux-kernel@vger.kernel.org \
    /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.