LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Nadia Derbey <Nadia.Derbey@bull.net>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
matthltc@us.ibm.com
Subject: Re: [RFC PATCH 4/4] [RESEND] Recomputing msgmni on memory add / remove
Date: Tue, 15 Jan 2008 18:40:52 +0900 [thread overview]
Message-ID: <20080115182402.6DBD.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <478C76D4.3010700@bull.net>
> Yasunori Goto wrote:
> > Hello Nadia-san.
> >
> >
> >>@@ -118,6 +122,10 @@ struct ipc_namespace {
> >> size_t shm_ctlall;
> >> int shm_ctlmni;
> >> int shm_tot;
> >>+
> >>+#ifdef CONFIG_MEMORY_HOTPLUG
> >>+ struct notifier_block ipc_memory_hotplug;
> >>+#endif
> >> };
> >
> >
> > I'm sorry, but I don't see why each ipc namespace must have each callbacks
> > of memory hotplug.
> > I prefer only one callback for each subsystem, not for each namespace.
> > In addition, the recompute_msgmni() calculation looks very similar for
> > all ipc namespace.
> > Or do you wish each ipc namespace have different callback for the future?
> >
>
> Actually, this is what I wanted to do at the very beginning: have a
> single callback that would recompute the msgmni for each ipc namespace.
> But the issue here is that the namespaces are not linked to each other,
> so I had no simple way to go through all the namespaces.
> I solved the issue by having a callback for any single ipc namespace and
> make it recompute the msgmni value for itslef.
The recompute_msg() must be called when new ipc_namespace is created/removed
as you mentioned. I think namespaces should be linked each other for it
in the end....
> >
> > BTW, have you ever tested this patch? If you don't have any test environment
> > for memory hotplug code, then I'll check it. :-)
>
> Well, I tested it but not in "real configuration": what I did is that I
> changed the status by hand under sysfs to offline. I also changed
> remove_memory() in mm/memory_hotplug.c in the following way (instead of
> returninf EINVAL):
> 1) decrease the total_ram pages
> 2) call memory_notify(MEM_OFFLINE, NULL)
>
> and checked that the msgmni was recomputed.
You can also online again after offline by writing sysfs.
> But sure, if you are candidate to test it, that would be great!
Ok. I'll check it too.
Bye.
--
Yasunori Goto
next prev parent reply other threads:[~2008-01-15 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 15:54 [RFC PATCH 0/4] [RESEND] Change default MSGMNI tunable to scale with lowmem Nadia.Derbey
2008-01-14 15:54 ` [RFC PATCH 1/4] [RESEND] Scaling msgmni to the amount of lowmem Nadia.Derbey
2008-01-14 15:54 ` [RFC PATCH 2/4] [RESEND] Scaling msgmni to the number of ipc namespaces Nadia.Derbey
2008-01-14 15:54 ` [RFC PATCH 3/4] [RESEND] Defining the slab_memory_callback priority as a constant Nadia.Derbey
2008-01-14 15:54 ` [RFC PATCH 4/4] [RESEND] Recomputing msgmni on memory add / remove Nadia.Derbey
2008-01-15 8:07 ` Yasunori Goto
2008-01-15 9:03 ` Nadia Derbey
2008-01-15 9:40 ` Yasunori Goto [this message]
2008-01-15 10:16 ` Nadia Derbey
2008-01-15 9:06 ` [RFC PATCH 0/4] [RESEND] Change default MSGMNI tunable to scale with lowmem Nadia Derbey
2008-01-15 9:21 ` Matt Helsley
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=20080115182402.6DBD.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=Nadia.Derbey@bull.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthltc@us.ibm.com \
--subject='Re: [RFC PATCH 4/4] [RESEND] Recomputing msgmni on memory add / remove' \
/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
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).