Messages in this thread | | | From | KOSAKI Motohiro <> | Subject | Re: [patch 1/7 -mm] oom: filter tasks not sharing the same cpuset | Date | Tue, 16 Feb 2010 15:01:33 +0900 (JST) |
| |
typo.
> But this explanation is irrelevant and meaningless. CPUSET can change
s/CPUSET/mempolicy/
> restricted node dynamically. So, the tsk->mempolicy at oom time doesn't > represent the place of task's usage memory. plus, OOM_DISABLE can > always makes undesirable result. it's not special in this case. > > The fact is, both current and your heuristics have a corner case. it's > obvious. (I haven't seen corner caseless heuristics). then talking your > patch's merit doesn't help to merge the patch. The most important thing > is, we keep no regression. personally, I incline your one. but It doesn't > mean we can ignore its demerit. > > >
| |