From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Cal Peake <cp@absolutedigital.net>, Andrew Morton <akpm@osdl.org>,
Randy Dunlap <rdunlap@xenotime.net>,
Jan Beulich <jbeulich@novell.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Undeprecate the sysctl system call
Date: Wed, 18 Oct 2006 14:41:51 +0200 [thread overview]
Message-ID: <200610181441.51748.ak@suse.de> (raw)
In-Reply-To: <1161173741.9363.22.camel@localhost.localdomain>
On Wednesday 18 October 2006 14:15, Alan Cox wrote:
> > Anyways, imho the right solution is to remove the numerical
> > sysctl infrastructure (including most of sysctl.h), but keep
> > sys_sysctl() with a small mapping table that maps the few
> > numerical sysctls (mostly KERN_VERSION) that are actually used to
> > path names internally. The rest should be ENOSYS.
>
> More work for less compatibility, that doesn't sound very clever.
It's less work long term, mostly because all the rejects for sysctl.h will
go away. And it's more compatible than just removing sysctl(2) completely.
The main reason i think at least emulating KERN_VERSION is a good idea is that
it will save a bit of time with older executables who do this
on every startup. /proc/sys/* is a little slow to do that often.
Normally sysctls are not that time critical so this is really a
exception.
-Andi
next prev parent reply other threads:[~2006-10-18 12:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 15:59 config SYSCTL_SYSCALL Jan Beulich
2006-10-17 16:19 ` Randy Dunlap
2006-10-17 18:17 ` [PATCH] Restore sysctl syscall option for non-embedded users Cal Peake
2006-10-17 22:11 ` Alan Cox
2006-10-17 21:59 ` Cal Peake
2006-10-17 22:00 ` Andrew Morton
2006-10-17 23:09 ` [PATCH] Undeprecate the sysctl system call Cal Peake
2006-10-17 23:19 ` Alan Cox
2006-10-18 3:41 ` Eric W. Biederman
2006-10-18 11:02 ` Alan Cox
2006-10-18 11:33 ` Andi Kleen
2006-10-18 12:15 ` Alan Cox
2006-10-18 12:41 ` Andi Kleen [this message]
2006-10-18 12:59 ` Alan Cox
2006-10-18 13:08 ` Andi Kleen
2006-10-18 16:20 ` [PATCHv2] " Cal Peake
2006-10-18 16:28 ` Andi Kleen
2006-10-18 16:41 ` Alan Cox
2006-10-18 19:31 ` Andrew Morton
2006-10-18 22:13 ` Alan Cox
2006-10-19 15:09 ` [PATCH] " Eric W. Biederman
2006-10-19 16:35 ` Alan Cox
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=200610181441.51748.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cp@absolutedigital.net \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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