OpenVZ Forum


Home » Mailing lists » Devel » [PATCH 5/20] Introduce struct upid
Re: [PATCH 5/20] Introduce struct upid [message #16477 is a reply to message #15827] Sat, 08 September 2007 02:16 Go to previous message
Sukadev Bhattiprolu is currently offline  Sukadev Bhattiprolu
Messages: 413
Registered: August 2006
Senior Member
Andrew Morton [akpm@linux-foundation.org] wrote:
| 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.

Sorry, we did not respond to this yet :-)

Well, every process has at least one 'struct upid'. The only "cost"
I see with size [1] is having to subtract 1 in create_pid_cachep().

Besides, we create/initialize the 'struct pid' for the idle process
by hand (see INIT_STRUCT_PID in init_task.h).

If we set this size to [0] now, we would need to dynamically allocate
a 'struct upid' during early boot and attach this upid to init_struct_pid.

Or is there a easy way to attach a 'upid' to init_struct_pid, statically ?

Suka
 
Read Message
Read Message
Read Message
Previous Topic: containers access control 'roadmap'
Next Topic: task->tgid conversion in fs/locks.c
Goto Forum:
  


Current Time: Mon Aug 04 04:47:09 GMT 2025

Total time taken to generate the page: 1.38042 seconds