[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48213A66.5030502@bull.net>
Date: Wed, 07 May 2008 07:13:10 +0200
From: Nadia Derbey <Nadia.Derbey@...l.net>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: containers@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, cmm@...ibm.com,
akpm@...ux-foundation.org
Subject: Re: [PATCH 1/8] Scaling msgmni to the amount of lowmem
Luck, Tony wrote:
>>Well, this printk had been suggested by somebody (sorry I don't remember
>>who) when I first submitted the patch. Actually I think it might be
>>useful for a sysadmin to be aware of a change in the msgmni value: we
>>have the message not only at boot time, but also each time msgmni is
>>recomputed because of a change in the amount of memory.
>
>
> If the message is directed at the system administrator, then it would
> be nice if there were some more meaningful way to show the namespace
> that is affected than just printing the hex address of the kernel structure.
>
> As the sysadmin for my test systems, printing the hex address is mildly
> annoying ... I now have to add a new case to my scripts that look at
> dmesg output for unusual activity.
>
> Is there some better "name for a namespace" than the address? Perhaps
> the process id of the process that instantiated the namespace???
>
Unfortunately no when we are inside an ipc namespace, we don't have such
interesting informations. But I agree with you, an address is not
readable enough. I'll try to find a solution.
Regards,
Nadia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists