Re: [PATCH] Link breaks for large NR_CPUS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Nov 05, 2003 at 10:18:38AM -0500, Martin Hicks wrote:
> 
> ext2 & ext3 lists,
> 
> Attatched is a patch that allows ext2 and ext3 to link correctly when
> the kernel is configured with a large NR_CPUS.  We do have an immediate
> need for this patch.

That's run correctly, I assume....

> Any opinions on this?  The per-cpu lists are causing the kmalloc to fail
> due to allocating more than the max.

vmalloc()'s are not free.  They burn kmap address space, TLB entries,
etc.  How many CPU's are necessary before we run into problems,
anyway?

I'd be much happier if there was a kvmalloc() call which resolved to
either kmalloc() or vmalloc() depending on how insane the number of
CPU's were, or if kvmalloc() programmatically made the determination
at runtime, and kvfree() checked the address to determine whether it
was a kmalloc()-returned address or a vmalloc()-returned address, and
called kfree() or vfree() as appropriate.

						 - Ted


_______________________________________________

Ext3-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ext3-users

[Index of Archives]         [Linux RAID]     [Kernel Development]     [Red Hat Install]     [Video 4 Linux]     [Postgresql]     [Fedora]     [Gimp]     [Yosemite News]

  Powered by Linux