Pete Zaitcev wrote:
> be about time to think about your data structures a little more.
> I'll let Andi to remind you about the performance impact (vmalloc
> area is outside of the big TLB area).
Offer an alternative? :) Linked list costs us as much or MORE for
->next as the gid_t. kmalloc() doesn't work for previous reasoning. I
considered a list of gid arr[256] or similar. A voice reminds me that
it doesn't impact us noticably in real use. Now, maybe other
architectures will find a good reason to switch to kmalloc() list of
smaller arrays, and the associated complextities or something else more
clever.
>>hmm, I haven't heard anything about them - can you offer an email or URL?
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0010.0/0788.html
Thanks - will check it..
-- Tim Hockin Systems Software Engineer Sun Microsystems, Linux Kernel Engineering thockin@sun.com- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Nov 15 2002 - 22:00:35 EST