From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "serge.hallyn@canonical.com" <serge.hallyn@canonical.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pavel Emelianov <xemul@parallels.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"jmorris@namei.org" <jmorris@namei.org>,
"cmetcalf@tilera.com" <cmetcalf@tilera.com>,
"joe.korty@ccur.com" <joe.korty@ccur.com>,
"dhowells@redhat.com" <dhowells@redhat.com>,
"dledford@redhat.com" <dledford@redhat.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"serue@us.ibm.com" <serue@us.ibm.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
"devel@openvz.org" <devel@openvz.org>,
"mtk.manpages@gmail.com" <mtk.manpages@gmail.com>
Subject: Re: [PATCH v8 2/5] ipc: add sysctl to specify desired next object id
Date: Thu, 25 Oct 2012 11:53:10 +0400 [thread overview]
Message-ID: <5088EFE6.2040900@parallels.com> (raw)
In-Reply-To: <20121024144123.0a77584b.akpm@linux-foundation.org>
25.10.2012 01:41, Andrew Morton пишет:
> On Wed, 24 Oct 2012 19:35:09 +0400
> Stanislav Kinsbursky <skinsbursky@parallels.com> wrote:
>
>> This patch adds 3 new variables and sysctls to tune them (by one "next_id"
>> variable for messages, semaphores and shared memory respectively).
>> This variable can be used to set desired id for next allocated IPC object.
>> By default it's equal to -1 and old behaviour is preserved.
>> If this variable is non-negative, then desired idr will be extracted from it
>> and used as a start value to search for free IDR slot.
>>
>> Notes:
>> 1) this patch doesn't garantee, that new object will have desired id. So it's
>> up to user space how to handle new object with wrong id.
>> 2) After sucessfull id allocation attempt, "next_id" will be set back to -1
>> (if it was non-negative).
>>
>> --- a/ipc/ipc_sysctl.c
>> +++ b/ipc/ipc_sysctl.c
>> @@ -158,6 +158,7 @@ static int proc_ipcauto_dointvec_minmax(ctl_table *table, int write,
>>
>> static int zero;
>> static int one = 1;
>> +static int int_max = INT_MAX;
>>
>> static struct ctl_table ipc_kern_table[] = {
>> {
>> @@ -227,6 +228,33 @@ static struct ctl_table ipc_kern_table[] = {
>> .extra1 = &zero,
>> .extra2 = &one,
>> },
>> + {
>> + .procname = "sem_next_id",
>> + .data = &init_ipc_ns.ids[IPC_SEM_IDS].next_id,
>> + .maxlen = sizeof(init_ipc_ns.ids[IPC_SEM_IDS].next_id),
>> + .mode = 0644,
>> + .proc_handler = proc_ipc_dointvec_minmax,
>> + .extra1 = &zero,
>> + .extra2 = &int_max,
>> + },
>> + {
>> + .procname = "msg_next_id",
>> + .data = &init_ipc_ns.ids[IPC_MSG_IDS].next_id,
>> + .maxlen = sizeof(init_ipc_ns.ids[IPC_MSG_IDS].next_id),
>> + .mode = 0644,
>> + .proc_handler = proc_ipc_dointvec_minmax,
>> + .extra1 = &zero,
>> + .extra2 = &int_max,
>> + },
>> + {
>> + .procname = "shm_next_id",
>> + .data = &init_ipc_ns.ids[IPC_SHM_IDS].next_id,
>> + .maxlen = sizeof(init_ipc_ns.ids[IPC_SHM_IDS].next_id),
>> + .mode = 0644,
>> + .proc_handler = proc_ipc_dointvec_minmax,
>> + .extra1 = &zero,
>> + .extra2 = &int_max,
>> + },
>> {}
>> };
>
> ipc_kern_table[] is (badly) documented in
> Documentation/sysctl/kernel.txt. Can we at least mention these
> controls in there? Better, create a new way of properly documenting
> each control and document these three in that manner? Better still,
> document all the other ones as well ;)
>
Yes, sure. I'll do my best.
> The patch adds these controls to CONFIG_CHECKPOINT_RESTORE=n kernels.
> Why is this?
>
I'll fix this.
--
Best regards,
Stanislav Kinsbursky
next prev parent reply other threads:[~2012-10-25 7:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 15:34 [RFC PATCH v8 0/5] IPC: checkpoint/restore in userspace enhancements Stanislav Kinsbursky
2012-10-24 15:35 ` [PATCH v8 1/5] ipc: remove forced assignment of selected message Stanislav Kinsbursky
2012-10-24 15:35 ` [PATCH v8 2/5] ipc: add sysctl to specify desired next object id Stanislav Kinsbursky
2012-10-24 21:41 ` Andrew Morton
2012-10-25 7:53 ` Stanislav Kinsbursky [this message]
2012-10-24 15:35 ` [PATCH v8 3/5] ipc: message queue receive cleanup Stanislav Kinsbursky
2012-10-24 15:35 ` [PATCH v8 4/5] ipc: message queue copy feature introduced Stanislav Kinsbursky
2012-10-24 21:41 ` Andrew Morton
2012-10-24 15:35 ` [PATCH v8 5/5] test: IPC message queue copy feture test Stanislav Kinsbursky
2012-10-24 21:42 ` [RFC PATCH v8 0/5] IPC: checkpoint/restore in userspace enhancements Andrew Morton
2012-12-18 20:36 ` Andrew Morton
2012-12-20 4:06 ` Stanislav Kinsbursky
2012-12-20 20:47 ` Andrew Morton
2012-12-21 20:46 ` Stanislav Kinsbursky
2012-12-21 21:57 ` Sasha Levin
2012-12-22 15:43 ` Sasha Levin
2013-01-09 8:24 ` Stanislav Kinsbursky
2013-01-14 6:31 ` Sasha Levin
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=5088EFE6.2040900@parallels.com \
--to=skinsbursky@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=cmetcalf@tilera.com \
--cc=devel@openvz.org \
--cc=dhowells@redhat.com \
--cc=dledford@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=joe.korty@ccur.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=serge.hallyn@canonical.com \
--cc=serue@us.ibm.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=will.deacon@arm.com \
--cc=xemul@parallels.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;
as well as URLs for NNTP newsgroup(s).