public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@openvz.org>
To: Pierre Peiffer <pierre.peiffer@bull.net>
Cc: Cedric Le Goater <clg@fr.ibm.com>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	containers@lists.osdl.org
Subject: Re: [PATCH 2.6.24-rc3-mm1] IPC: make struct ipc_ids static in ipc_namespace
Date: Fri, 23 Nov 2007 12:27:15 +0300	[thread overview]
Message-ID: <47469CF3.1030200@openvz.org> (raw)
In-Reply-To: <47469630.3060807@bull.net>

Pierre Peiffer wrote:
> Hi,
> 
> 	Thanks for reviewing this !
> 
> Pavel Emelyanov wrote:
>> Pavel Emelyanov wrote:
>>> Cedric Le Goater wrote:
>>>> Pierre Peiffer wrote:
>> [snip]
>>
>>>> Pavel, what do you think of it ? 
>>> Looks sane, good catch, Pierre.
>>>
>>> But I'd find out whether these three ipc_ids intersect any 
>>> cache-line. In other words I'd mark the struct ipc_ids as
>>> ____cacheline_aligned and checked for any differences.
>> BTW! It might be also useful to keep ipc_ids closer to their
>> sysctl parameters.
>>
> 
> It makes sense indeed.
> 
> That would mean to have something like this, right ?

Yup :)

> struct ipc_namespace {
> 	struct kref	kref;
> 
> 	struct ipc_ids	sem_ids;
> 	int		sem_ctls[4];
> 	int		used_sems;
> 
> 	struct ipc_ids	msg_ids;
> 	int		msg_ctlmax;
> 	int		msg_ctlmnb;
> 	int		msg_ctlmni;
> 	atomic_t	msg_bytes;
> 	atomic_t	msg_hdrs;
> 
> 	struct ipc_ids	shm_ids;
> 	size_t		shm_ctlmax;
> 	size_t		shm_ctlall;
> 	int		shm_ctlmni;
> 	int		shm_tot;
> };
> 
> After a quick look, that implies to rework a little bit procfs... othwise, it's
> not a big deal as I can see.

Thanks!

> P.
> 
>>>> Acked-by: Cedric Le Goater <clg@fr.ibm.com>
>>>>
>>>> Thanks,
>>> Thanks,
>>> Pavel
>>>
>>>> C.
>> [snip]
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/
>>
> 


  reply	other threads:[~2007-11-23  9:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-22 14:54 [PATCH 2.6.24-rc3-mm1] IPC: make struct ipc_ids static in ipc_namespace Pierre Peiffer
2007-11-23  7:26 ` Cedric Le Goater
2007-11-23  7:37   ` Pavel Emelyanov
2007-11-23  8:02     ` Pavel Emelyanov
2007-11-23  8:58       ` Pierre Peiffer
2007-11-23  9:27         ` Pavel Emelyanov [this message]
2007-11-23 10:49           ` Pierre Peiffer
2007-11-23 11:06             ` Pavel Emelyanov
2007-11-23 11:40               ` Pierre Peiffer

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=47469CF3.1030200@openvz.org \
    --to=xemul@openvz.org \
    --cc=akpm@linux-foundation.org \
    --cc=clg@fr.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.peiffer@bull.net \
    /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