From: Dave Hansen <haveblue@us.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
serue@us.ibm.com, frankeh@watson.ibm.com, clg@fr.ibm.com,
Herbert Poetzl <herbert@13thfloor.at>,
Sam Vilain <sam@vilain.net>
Subject: Re: sysctls inside containers
Date: Mon, 06 Mar 2006 08:27:16 -0800 [thread overview]
Message-ID: <1141662436.9274.25.camel@localhost.localdomain> (raw)
In-Reply-To: <m1veuucxnv.fsf@ebiederm.dsl.xmission.com>
On Sat, 2006-03-04 at 03:27 -0700, Eric W. Biederman wrote:
> > I don't see an immediately clear solution on how to containerize sysctls
> > properly. The entire construct seems to be built around getting data
> > from in and out of global variables and into /proc files.
>
> I successfully handled pid_max. So while it is awkward you can get
> per task values in and out if sysctl.
This:
http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/ebiederm/linux-2.6-ns.git;a=commitdiff;h=1150082e0bae41a3621043b4c5ce15e9112884fa
sir, is a hack :)
We can't possibly do that for each and every sysctl variable. It would
mean about fourteen billion duplicated _conv() functions.
I'm wondering if, instead of having the .data field in that table, we
can have a function pointer which, when called, gives a pointer to the
data. I'll give it a shot.
-- Dave
next prev parent reply other threads:[~2006-03-06 16:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-20 15:45 Which of the virtualization approaches is more suitable for kernel? Kirill Korotaev
2006-02-20 16:12 ` Herbert Poetzl
2006-02-21 16:00 ` Kirill Korotaev
2006-02-21 20:33 ` Sam Vilain
2006-02-21 23:50 ` Herbert Poetzl
2006-02-22 10:09 ` [Devel] " Kir Kolyshkin
2006-02-22 15:26 ` Eric W. Biederman
2006-02-23 12:02 ` Kir Kolyshkin
2006-02-23 13:25 ` Eric W. Biederman
2006-02-23 14:00 ` Kir Kolyshkin
2006-02-24 21:44 ` Eric W. Biederman
2006-02-24 23:01 ` Herbert Poetzl
2006-02-27 17:42 ` Dave Hansen
2006-02-27 21:14 ` Eric W. Biederman
2006-02-27 21:35 ` Dave Hansen
2006-02-27 21:56 ` Eric W. Biederman
2006-03-04 3:17 ` sysctls inside containers Dave Hansen
2006-03-04 10:27 ` Eric W. Biederman
2006-03-06 16:27 ` Dave Hansen [this message]
2006-03-06 17:08 ` Herbert Poetzl
2006-03-06 17:18 ` Dave Hansen
2006-03-06 18:56 ` Eric W. Biederman
2006-03-10 10:17 ` Kirill Korotaev
2006-03-10 13:22 ` Eric W. Biederman
2006-03-10 10:19 ` Kirill Korotaev
2006-03-10 11:55 ` Eric W. Biederman
2006-03-10 18:58 ` Dave Hansen
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=1141662436.9274.25.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=clg@fr.ibm.com \
--cc=ebiederm@xmission.com \
--cc=frankeh@watson.ibm.com \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@vilain.net \
--cc=serue@us.ibm.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.