new/malloc NUMA awareness

[tbp <tbptbp at gmail dot com>]

All my "binded" allocations are supposed to go through VirtualAlloc &
co on win32, but i've traced back a performance issue to a dandling
new somewhere in my code handling me non cpu-local memory (in a binded
thread).
Now where it gets really weird is that i get memory with proper
affinity when i launch the gcc compiled binary from msvc2k5 (ie thru
ctrl-f5), and only in that case.
It's kinda hard to debug such interaction.

To be clear, i don't expect malloc/new to hand me memory with proper
affinity as m$' own runtime doesn't bother to. But i'm a bit puzzled
by that inconsistent behaviour. What's the unwritten rule?

bi-k8 box, xp sp2,
Using built-in specs.
Target: i686-pc-cygwin
Configured with: ../configure --prefix=/usr/local/gcc-4.2-20060624
--enable-languages=c,c++ --enable
-threads=posix --with-system-zlib --disable-checking --disable-nls
--disable-shared --disable-win32-
registry --verbose --enable-bootstrap --with-gcc --with-gnu-ld
--with-gnu-as --with-cpu=k8
Thread model: posix
gcc version 4.2.0 20060624 (experimental)

Attachment: cyg.txt
Description: Text document

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/