... mm1.orig/include/linux/vmalloc.h 2008-03-19 18:17:42.093443900 -0700 ... rc5-mm1/include/linux/vmalloc.h 2008-03-19 18:27:20.150422445 -0700 ... -mm1.orig/mm/vmalloc.c 2008-03-19 18:18:02.689633934 -0700 ... -rc5-mm1/mm/vmalloc.c 2008-03-19 18:27:20.150422445 -0700 ...

linux-kernel - Eric Dumazet - Mar 21 2008 - 03:55

On Tue, 18 Sep 2007, Christoph Lameter wrote: > Index: linux-2.6/include/linux/mm.h > =================================================================== > --- linux-2.6.orig/include/linux/mm.h 2007-09-17 21:46:06.000000000 -0700 > +++ linux-2.6/

linux-kernel - David Rientjes - Sep 19 2007 - 02:32

On 19 Sep 2007, at 07:32, David Rientjes wrote: > On Tue, 18 Sep 2007, Christoph Lameter wrote: >> Index: linux-2.6/include/linux/mm.h >> =================================================================== >> --- linux-2.6.orig/include/linux/mm.h 2007

linux-kernel - Anton Altaparmakov - Sep 19 2007 - 03:24

On Wed, 19 Sep 2007, Anton Altaparmakov wrote: > Although it may cause a problem as highmem.h also includes mm.h so a bit of > trickery may be needed to get it to compile... > > I suspect that is_vmalloc_addr() should not be in linux/mm.h at all

linux-kernel - David Rientjes - Sep 19 2007 - 05:19

On 19 Sep 2007, at 10:19, David Rientjes wrote: > On Wed, 19 Sep 2007, Anton Altaparmakov wrote: >> Although it may cause a problem as highmem.h also includes mm.h so >> a bit of >> trickery may be needed to get it to compile... >> >> I suspect

linux-kernel - Anton Altaparmakov - Sep 19 2007 - 09:23

On Wed, 19 Sep 2007, Anton Altaparmakov wrote: > There even is such a function already in mm/sparse.c::vaddr_in_vmalloc_area() > with pretty identical content. I would suggest either this new inline should > go away completely and use the existing

linux-kernel - Christoph Lameter - Sep 19 2007 - 13:29

On Wed, 19 Sep 2007, Anton Altaparmakov wrote: > I suspect that is_vmalloc_addr() should not be in linux/mm.h at all and should > be in linux/vmalloc.h instead and vmalloc.h should include linux/highmem.h. > That would be more sensible than sticking

linux-kernel - Christoph Lameter - Sep 19 2007 - 13:29

On 19 Sep 2007, at 18:29, Christoph Lameter wrote: > On Wed, 19 Sep 2007, Anton Altaparmakov wrote: >> There even is such a function already in mm/ >> sparse.c::vaddr_in_vmalloc_area() >> with pretty identical content. I would suggest either this

linux-kernel - Anton Altaparmakov - Sep 19 2007 - 13:52

On 19 Sep 2007, at 18:29, Christoph Lameter wrote: > On Wed, 19 Sep 2007, Anton Altaparmakov wrote: >> I suspect that is_vmalloc_addr() should not be in linux/mm.h at >> all and should >> be in linux/vmalloc.h instead and vmalloc.h should include

linux-kernel - Anton Altaparmakov - Sep 19 2007 - 13:52

On Tue, 18 Sep 2007, Christoph Lameter wrote: > Index: linux-2.6/include/linux/mm.h > =================================================================== > --- linux-2.6.orig/include/linux/mm.h 2007-09-17 21:46:06.000000000 -0700 > +++ linux-2.6/

linux-fsdevel - David Rientjes - Sep 19 2007 - 02:32

On 19 Sep 2007, at 07:32, David Rientjes wrote: > On Tue, 18 Sep 2007, Christoph Lameter wrote: >> Index: linux-2.6/include/linux/mm.h >> =================================================================== >> --- linux-2.6.orig/include/linux/mm.h 2007

linux-fsdevel - Anton Altaparmakov - Sep 19 2007 - 03:24

On Wed, 19 Sep 2007, Anton Altaparmakov wrote: > Although it may cause a problem as highmem.h also includes mm.h so a bit of > trickery may be needed to get it to compile... > > I suspect that is_vmalloc_addr() should not be in linux/mm.h at all

linux-fsdevel - David Rientjes - Sep 19 2007 - 05:19

On 19 Sep 2007, at 10:19, David Rientjes wrote: > On Wed, 19 Sep 2007, Anton Altaparmakov wrote: >> Although it may cause a problem as highmem.h also includes mm.h so >> a bit of >> trickery may be needed to get it to compile... >> >> I suspect

linux-fsdevel - Anton Altaparmakov - Sep 19 2007 - 09:23

On Wed, 19 Sep 2007, Anton Altaparmakov wrote: > I suspect that is_vmalloc_addr() should not be in linux/mm.h at all and should > be in linux/vmalloc.h instead and vmalloc.h should include linux/highmem.h. > That would be more sensible than sticking

linux-fsdevel - Christoph Lameter - Sep 19 2007 - 13:29

On Wed, 19 Sep 2007, Anton Altaparmakov wrote: > There even is such a function already in mm/sparse.c::vaddr_in_vmalloc_area() > with pretty identical content. I would suggest either this new inline should > go away completely and use the existing

linux-fsdevel - Christoph Lameter - Sep 19 2007 - 13:29

On 19 Sep 2007, at 18:29, Christoph Lameter wrote: > On Wed, 19 Sep 2007, Anton Altaparmakov wrote: >> I suspect that is_vmalloc_addr() should not be in linux/mm.h at >> all and should >> be in linux/vmalloc.h instead and vmalloc.h should include

linux-fsdevel - Anton Altaparmakov - Sep 19 2007 - 13:52

On 19 Sep 2007, at 18:29, Christoph Lameter wrote: > On Wed, 19 Sep 2007, Anton Altaparmakov wrote: >> There even is such a function already in mm/ >> sparse.c::vaddr_in_vmalloc_area() >> with pretty identical content. I would suggest either this

linux-fsdevel - Anton Altaparmakov - Sep 19 2007 - 13:52

On Fri, 21 Mar 2008, Eric Dumazet wrote: > I would love to see NUMA information as well on vmallocinfo, but have > currently no available time to prepare a patch. Ok. Easy to add. -- To unsubscribe from this list: send the line "unsubscribe linux

linux-kernel - Christoph Lameter - Mar 21 2008 - 13:32

... is reported only once include/linux/mm.h:1166: error: for each function it appears in.) so I don't know what you're talking about. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger. ...

linux-kernel - David Rientjes - Sep 19 2007 - 04:09

... only once > include/linux/mm.h:1166: error: for each function it appears in.) > > so I don't know what you're talking about. Just a compile failure not inherently broken! Add: #include to the top of linux/mm.h and it should ...

linux-kernel - Anton Altaparmakov - Sep 19 2007 - 04:44