On Wednesday 31 October 2007 21:42, Peter Zijlstra wrote:

On Wed, 2007-10-31 at 14:51 +1100, Nick Piggin wrote:

quoted

On Wednesday 31 October 2007 03:04, Peter Zijlstra wrote:

quoted

Allow PF_MEMALLOC to be set in softirq context. When running softirqs
from a borrowed context save current->flags, ksoftirqd will have its
own task_struct.

What's this for? Why would ksoftirqd pick up PF_MEMALLOC? (I guess
that some networking thing must be picking it up in a subsequent patch,
but I'm too lazy to look!)... Again, can you have more of a rationale in
your patch headers, or ref the patch that uses it... thanks

Right, I knew I was forgetting something in these changelogs.

The network stack does quite a bit of packet processing from softirq
context. Once you start swapping over network, some of the packets want
to be processed under PF_MEMALLOC.

Hmm... what about processing from interrupt context?