On Wed, 2007-10-31 at 14:51 +1100, Nick Piggin wrote: > On Wednesday 31 October 2007 03:04, Peter Zijlstra wrote: > > 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. See patch 23/33.
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- Re: [PATCH 06/33] mm: allow PF_MEMALLOC from softirq context
- From: Nick Piggin <[email protected]>
- Re: [PATCH 06/33] mm: allow PF_MEMALLOC from softirq context
- References:
- [PATCH 00/33] Swap over NFS -v14
- From: Peter Zijlstra <[email protected]>
- [PATCH 06/33] mm: allow PF_MEMALLOC from softirq context
- From: Peter Zijlstra <[email protected]>
- Re: [PATCH 06/33] mm: allow PF_MEMALLOC from softirq context
- From: Nick Piggin <[email protected]>
- [PATCH 00/33] Swap over NFS -v14
- Prev by Date: Re: [PATCH 05/33] mm: kmem_estimate_pages()
- Next by Date: Re: [PATCH 09/33] mm: system wide ALLOC_NO_WATERMARK
- Previous by thread: Re: [PATCH 06/33] mm: allow PF_MEMALLOC from softirq context
- Next by thread: Re: [PATCH 06/33] mm: allow PF_MEMALLOC from softirq context
- Index(es):
 |