Re: [PATCH] cpuset - rework cpuset_zone_allowed api

2006-12-08 Thread Andrew Morton
On Fri, 08 Dec 2006 03:21:52 -0800 Paul Jackson <[EMAIL PROTECTED]> wrote: > From: Paul Jackson <[EMAIL PROTECTED]> > > Elaborate the API for calling cpuset_zone_allowed(), so that users > have to explicitly choose between the two variants: > > cpuset_zone_allowed_hardwall() > cpuset_zone_al

Re: [PATCH] cpuset - rework cpuset_zone_allowed api

2006-12-08 Thread Paul Jackson
Paul M wrote: > While you're changing this, is there a good reason not to check > is_mem_exclusive() *before* taking callback_mutex and calling > nearest_exclusive_ancestor()? > > something like: > > rcu_read_lock(); > exc = is_mem_exclusive(rcu_dereference(current->cs)); > rcu_read_unlock(); > i

Re: [PATCH] cpuset - rework cpuset_zone_allowed api

2006-12-08 Thread Paul Menage
On 12/8/06, Paul Jackson <[EMAIL PROTECTED]> wrote: -int __cpuset_zone_allowed(struct zone *z, gfp_t gfp_mask) +int __cpuset_zone_allowed_softwall(struct zone *z, gfp_t gfp_mask) { int node; /* node that zone z is on */ const struct cpuset *cs;/* cu