Messages in this thread | | | Date | Sun, 8 Mar 2009 09:53:44 -0700 | Subject | Re: [patch -mm] cpusets: add memory_slab_hardwall flag | From | Paul Menage <> |
| |
On Sun, Mar 8, 2009 at 9:27 AM, David Rientjes <rientjes@google.com> wrote: > +/** > + * current_cpuset_object_allowed - can a slab object be allocated on a node? > + * @node: the node for object allocation > + * @flags: allocation flags > + * > + * Return non-zero if object is allowed, zero otherwise. > + */ > +int current_cpuset_object_allowed(int node, gfp_t flags) > +{ > + return !is_slab_hardwall(task_cs(current)) || > + cpuset_node_allowed_hardwall(node, flags); > +} > +
This should be in rcu_read_lock()/rcu_read_unlock() in order to safely dereference the result of task_cs(current)
I'll leave the actual memory allocator changes for others to comment on .
Paul -- 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/
| |