On Thu 19-07-12 16:56:18, Aneesh Kumar K.V wrote:
> Kamezawa Hiroyuki writes:
>
> >
> > We test RES_USAGE before taking hugetlb_lock. What prevents some other
> > thread from increasing RES_USAGE after that test?
> >
> > After walking the list we test RES_USAGE after dropping
Kamezawa Hiroyuki writes:
>
> We test RES_USAGE before taking hugetlb_lock. What prevents some other
> thread from increasing RES_USAGE after that test?
>
> After walking the list we test RES_USAGE after dropping hugetlb_lock.
> What prevents another thread from increment
(2012/07/19 18:41), Aneesh Kumar K.V wrote:
Li Zefan writes:
on 2012/7/19 10:55, Aneesh Kumar K.V wrote:
Andrew Morton writes:
On Wed, 18 Jul 2012 11:04:09 +0530
"Aneesh Kumar K.V" wrote:
From: "Aneesh Kumar K.V"
Since we cannot fail in hugetlb_cgroup_move_parent, we don't really
nee
Li Zefan writes:
> on 2012/7/19 10:55, Aneesh Kumar K.V wrote:
>
>> Andrew Morton writes:
>>
>>> On Wed, 18 Jul 2012 11:04:09 +0530
>>> "Aneesh Kumar K.V" wrote:
>>>
From: "Aneesh Kumar K.V"
Since we cannot fail in hugetlb_cgroup_move_parent, we don't really
need to check
on 2012/7/19 10:55, Aneesh Kumar K.V wrote:
> Andrew Morton writes:
>
>> On Wed, 18 Jul 2012 11:04:09 +0530
>> "Aneesh Kumar K.V" wrote:
>>
>>> From: "Aneesh Kumar K.V"
>>>
>>> Since we cannot fail in hugetlb_cgroup_move_parent, we don't really
>>> need to check whether cgroup have any change
Andrew Morton writes:
> On Wed, 18 Jul 2012 11:04:09 +0530
> "Aneesh Kumar K.V" wrote:
>
>> From: "Aneesh Kumar K.V"
>>
>> Since we cannot fail in hugetlb_cgroup_move_parent, we don't really
>> need to check whether cgroup have any change left after that. Also skip
>> those hstates for which w
On Wed, 18 Jul 2012 11:04:09 +0530
"Aneesh Kumar K.V" wrote:
> From: "Aneesh Kumar K.V"
>
> Since we cannot fail in hugetlb_cgroup_move_parent, we don't really
> need to check whether cgroup have any change left after that. Also skip
> those hstates for which we don't have any charge in this cg
On Wed, Jul 18, 2012 at 11:04:09AM +0530, Aneesh Kumar K.V wrote:
>From: "Aneesh Kumar K.V"
>
>Since we cannot fail in hugetlb_cgroup_move_parent, we don't really
>need to check whether cgroup have any change left after that. Also skip
>those hstates for which we don't have any charge in this cgro
From: "Aneesh Kumar K.V"
Since we cannot fail in hugetlb_cgroup_move_parent, we don't really
need to check whether cgroup have any change left after that. Also skip
those hstates for which we don't have any charge in this cgroup.
Based on an earlier patch from Wanpeng Li
Signed-off-by: Aneesh
9 matches
Mail list logo