From: Andrew Morton <akpm@linux-foundation.org>
To: xemul@openvz.org
Cc: devel@openvz.org, linux-kernel@vger.kernel.org,
containers@lists.osdl.org, oleg@tv-sign.ru, sukadev@us.ibm.com
Subject: Re: [PATCH 5/20] Introduce struct upid
Date: Tue, 14 Aug 2007 13:05:58 -0700 [thread overview]
Message-ID: <20070814130558.4b5e5e3f.akpm@linux-foundation.org> (raw)
In-Reply-To: <46BC506F.mailGJ711PNHE@openvz.org>
On Fri, 10 Aug 2007 15:47:59 +0400
xemul@openvz.org wrote:
> struct pid
> {
> atomic_t count;
> @@ -50,6 +50,8 @@ struct pid
> /* lists of tasks that use this pid */
> struct hlist_head tasks[PIDTYPE_MAX];
> struct rcu_head rcu;
> + int level;
> + struct upid numbers[1];
You can make this have size [0] now. It's a gcc extension and
is used elsewhere in the kernel.
next prev parent reply other threads:[~2007-08-14 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 11:47 [PATCH 5/20] Introduce struct upid xemul
2007-08-14 20:05 ` Andrew Morton [this message]
2007-09-08 2:16 ` sukadev
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=20070814130558.4b5e5e3f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=sukadev@us.ibm.com \
--cc=xemul@openvz.org \
/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