From: Andi Kleen <ak@linux.intel.com>
To: Andreas Schwab <schwab@redhat.com>
Cc: Amerigo Wang <amwang@redhat.com>,
linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Len Brown <len.brown@intel.com>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>,
Eric Paris <eparis@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Andy Shevchenko <ext-andriy.shevchenko@nokia.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/2] sysctl: remove sysctl syscall
Date: Tue, 19 Oct 2010 17:05:20 +0200 [thread overview]
Message-ID: <4CBDB3B0.8080605@linux.intel.com> (raw)
In-Reply-To: <m3lj5uff3h.fsf@hase.home>
On 10/19/2010 4:10 PM, Andreas Schwab wrote:
>> On 10/19/2010 10:22 AM, Amerigo Wang wrote:
>>> Remove the obsolete sysctl syscall. It was scheduled
>>> to be removed in Sept.
>>
>> I thought at least older glibc was still using it? Did anyone check
>> what happens if it sees no sysctl(2)?
> It will fall back reading from /proc/sys.
First that's slow (but ok), but that will fail if there is no /proc.
-Andi
next prev parent reply other threads:[~2010-10-19 15:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 8:22 [PATCH 1/2] sysctl: refactor __do_proc_doulongvec_minmax() Amerigo Wang
2010-10-19 8:22 ` [PATCH 2/2] sysctl: remove sysctl syscall Amerigo Wang
2010-10-19 13:22 ` Andi Kleen
2010-10-19 13:49 ` Eric W. Biederman
2010-10-19 15:04 ` Andi Kleen
2010-10-19 16:00 ` Eric W. Biederman
2010-10-20 6:06 ` Cong Wang
2010-10-20 13:54 ` Eric W. Biederman
2010-10-21 9:26 ` Cong Wang
2010-10-19 14:10 ` Andreas Schwab
2010-10-19 15:05 ` Andi Kleen [this message]
2010-10-20 5:41 ` Cong Wang
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=4CBDB3B0.8080605@linux.intel.com \
--to=ak@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=eparis@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=ext-andriy.shevchenko@nokia.com \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mingo@elte.hu \
--cc=rdunlap@xenotime.net \
--cc=schwab@redhat.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 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.