Re: [rfc] generic allocator and mspec driver

From: Jes Sorensen <>
Date: 2005-02-04 01:55:26
>>>>> "Robin" == Robin Holt <> writes:

Jack> Ugly hack. Isn't there a better way? (I know this isn't your
Jack> code & you probably don't like this either. I had hoped for a
Jack> cleaner solution in 2.6....)
>>  It's gross, ugly and I hate it ... not sure if there's a simpler
>> way.  Maybe we can use the same approach as the fbmem driver and do
>> it all in the mmap() function, I will have to investigate that.

Robin> If you do it in the mmap, all the pages will be allocated and
Robin> mapped on the node doing the map.  This will result in large
Robin> applications using multiple threads to incur _LARGE_ amounts of
Robin> numa traffic.  The first fault is critical for performance.


Is this because the applications will normally allocate their fetchops
in the main thread before spawning off the threads? If the mmap is
done by the thread that will 'own' the individual fetchop this
wouldn't be a problem? Sorry, just trying to understand the nature of
how these applications work, my knowledge of MPI etc. is ehm
... limited ;)

Jack> + /* + * Use the bte to ensure cache lines + * are actually
Jack> pulled from the + * processor back to the md.  + */ +
Jack> This doesn't need to be done if the memory was being used for
Jack> fetchops or uncached memory.
>>  I'll check.

Robin> The bte zero is needed for memory mapped cached (one of the
Robin> mechanisms here) and also ensures the memory is zereod out when
Robin> returned to the memory pool.

I already updated the  comment to state that we want the memory
zeroed in the pool.

To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to
More majordomo info at
Received on Thu Feb 3 10:03:38 2005

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:35 EST