Re: [PATCH] Allow __vmalloc with GFP_ATOMIC

On Fri, Apr 27, 2007 at 09:03:33PM -0700, Giridhar Pemmasani wrote: > Until 2.6.19, __vmalloc with GFP_ATOMIC was possible, but __get_vm_area_node > would allocate the node itself with GFP_KERNEL, causing a warning. In 2.6.19, > this was "fixed" by using the same flags that were passed to __vmalloc

Re: [PATCH] Allow __vmalloc with GFP_ATOMIC

--- Nick Piggin <[EMAIL PROTECTED]> wrote: >> The patch below uses bh disabled lock for vmlist_lock, so >> that __vmalloc can be used in interrupt context. > Hi Giri, > > I'm sure I've read the reason for this one before, but when you do patches > like these, can you include that reason in the c

Re: [PATCH] Allow __vmalloc with GFP_ATOMIC

Giridhar Pemmasani wrote: Until 2.6.19, __vmalloc with GFP_ATOMIC was possible, but __get_vm_area_node would allocate the node itself with GFP_KERNEL, causing a warning. In 2.6.19, this was "fixed" by using the same flags that were passed to __vmalloc also in __get_vm_area_node. However, __get_vm