diff options
| author | Miquel van Smoorenburg <mikevs@xs4all.net> | 2008-05-28 04:31:25 -0400 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2008-06-02 06:14:58 -0400 |
| commit | db9f600b96c16bb3c7f094e294fbdd370226ad86 (patch) | |
| tree | ac83fd33678c2e6efecbd7c96503db6cca1549ad /Documentation/eisa.txt | |
| parent | 75b19b790bec3ebffbf513405b27500e22270cbc (diff) | |
x86: pci-dma.c: use __GFP_NO_OOM instead of __GFP_NORETRY
On Wed, 2008-05-28 at 04:47 +0200, Andi Kleen wrote:
> > So... why not just remove the setting of __GFP_NORETRY? Why is it
> > wrong to oom-kill things in this case?
>
> When the 16MB zone overflows (which can be common in some workloads)
> calling the OOM killer is pretty useless because it has barely any
> real user data [only exception would be the "only 16MB" case Alan
> mentioned]. Killing random processes in this case is bad.
>
> I think for 16MB __GFP_NORETRY is ok because there should be
> nothing freeable in there so looping is useless. Only exception would be the
> "only 16MB total" case again but I'm not sure 2.6 supports that at all
> on x86.
>
> On the other hand d_a_c() does more allocations than just 16MB, especially
> on 64bit and the other zones need different strategies.
Okay, so how about this then ?
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'Documentation/eisa.txt')
0 files changed, 0 insertions, 0 deletions