[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-kernel
Subject:    Re: [RFC PATCH 1/5] Move task's RCU code to rcupdate.h
From:       "Paul E. McKenney" <paulmck () linux ! vnet ! ibm ! com>
Date:       2011-03-31 23:24:01
Message-ID: 20110331232401.GO2258 () linux ! vnet ! ibm ! com
[Download RAW message or body]

On Thu, Mar 31, 2011 at 01:31:36PM +0200, Peter Zijlstra wrote:
> On Mon, 2011-03-28 at 10:58 +0800, Lai Jiangshan wrote:
> > +struct task_rcu_struct {
> > +#ifdef CONFIG_PREEMPT_RCU
> > +       int rcu_read_lock_nesting;
> > +       char rcu_read_unlock_special;
> 
> Is there a good reason that's a char? It'll leave a 3 byte hole in this
> location.

No good reason.  Lai just copied the existing char from the task
struct into his task_rcu_struct, so not his fault.  ;-)

							Thanx, Paul

> > +       struct list_head rcu_node_entry;
> > +#ifdef CONFIG_TREE_PREEMPT_RCU
> > +       struct rcu_node *rcu_blocked_node;
> > +#endif /* #ifdef CONFIG_TREE_PREEMPT_RCU */
> > +#ifdef CONFIG_RCU_BOOST
> > +       struct rt_mutex *rcu_boost_mutex;
> > +#endif /* #ifdef CONFIG_RCU_BOOST */
> > +#endif /* #ifdef CONFIG_PREEMPT_RCU */
> > +}; 
--
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/
[prev in list] [next in list] [prev in thread] [next in thread]