Re: [patch for-3.7] mm, mempolicy: fix printing stack contents in numa_maps
From: David Rientjes <rientjes@google.com>
Date: 2012-10-17 19:50:24
Also in:
lkml
From: David Rientjes <rientjes@google.com>
Date: 2012-10-17 19:50:24
Also in:
lkml
On Wed, 17 Oct 2012, KOSAKI Motohiro wrote:
quoted
I think this refcounting is better than using task_lock().I don't think so. get_vma_policy() is used from fast path. In other words, number of atomic ops is sensible for allocation performance.
There are enhancements that we can make with refcounting: for instance, we may want to avoid doing it in the super-fast path when the policy is default_policy and then just do if (mpol != &default_policy) mpol_put(mpol);
Instead, I'd like to use spinlock for shared mempolicy instead of mutex.
Um, this was just changed to a mutex last week in commit b22d127a39dd
("mempolicy: fix a race in shared_policy_replace()") so that sp_alloc()
can be done with GFP_KERNEL, so I didn't consider reverting that behavior.
Are you nacking that patch, which you acked, now?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>