elf header bits for page migration support......
Tony,
As some of the readers of this list may know, I've been working on a
"manual page migration" facility for Altix. Basically this is intended
to allow a batch manager to move applications around on a large NUMA system. Further details and discussion can be found on the linux-mm lists, for example the thread starting at:
http://marc.theaimsgroup.com/?l=linux-mm&m1578651020174&w=2
Now given the existence of the memory migration code in the memory hotplug patch, the hard part of this project is not doing the migration, but figuring out what not to migrate (e. g. one doesn't want to migrate the shared pages of a shared library, for example). Currently, we are flagging files as libraries by using a file system extended attribute. But this is meeting with some resistance.
The alternative being suggested is to mark the elf header of object files that should only have shared pages migrated, or that should not be migrated (e. g. you don't want to migrate /bin/csh all the time.)
(We'll extend mmap() with a similar set of flags.)
So the question has come up, which bits in the elf header are available for such use. Apparently there is a bit of a muddle here and we need to get the "community" to agree.
So, I'm starting with linux-ia64. Here's a specific question to get the ball rolling:
Can I use some bits (I need 2) of p_flags of Elf64_Phdr for this purpose? If so, which bits?
If not which other fields can I use?
Note: The kernel and ld.so have to both be able to find the bits relatively easily.
Signature · 9 lines
Best Regards,
Ray
-----------------------------------------------
Ray Bryant
512-453-9679 (work) 512-507-7807 (cell)
[email protected] [email protected]
The box said: "Requires Windows 98 or better",
so I installed Linux.
-----------------------------------------------Quoted 21 lines · Ray Bryant
Tony,
As some of the readers of this list may know, I've been working on a
"manual page migration" facility for Altix. Basically this is intended
to allow a batch manager to move applications around on a large NUMA system. Further details and discussion can be found on the linux-mm lists, for example the thread starting at:http://marc.theaimsgroup.com/?l=linux-mm&m1578651020174&w=2
Now given the existence of the memory migration code in the memory hotplug patch, the hard part of this project is not doing the migration, but figuring out what not to migrate (e. g. one doesn't want to migrate the shared pages of a shared library, for example). Currently, we are flagging files as libraries by using a file system extended attribute. But this is meeting with some resistance.
The alternative being suggested is to mark the elf header of object files that should only have shared pages migrated, or that should not be migrated (e. g. you don't want to migrate
/bin/cshall the time.)
Quoted 5 lines
(We'll extend
mmap()with a similar set of flags.)So the question has come up, which bits in the elf header are available for such use. Apparently there is a bit of a muddle here and we need to get the "community" to agree.
Bits in elf header are very scare. Can you use an ELF segment like PT_GNU_EH_FRAME and PT_GNU_STACK?
H.J.
Quoted 3 lines
The alternative being suggested is to mark the elf header of object files that should only have shared pages migrated, or that should not be migrated (e. g. you don't want to migrate
/bin/cshall the time.)
No ... I'd like you to replicate shared pages (of /bin/bash ... I personally don't care what happens to the pages of /bin/csh :-)
Quoted 4 lines
Can I use some bits (I need 2) of
p_flagsofElf64_Phdrfor this purpose? If so, which bits?If not which other fields can I use?
I think H.J's suggestion of an extra section makes sense ... then you can go wild with as many bits as you can dream up uses for, rather than constraining yourself to squeeze into just 2 bits.
-Tony
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"H" = H J Lu <[email protected]> writes:
Quoted 7 lines · Ray Bryant
Quoted 7 lines
Tony,
The alternative being suggested is to mark the elf header of object files that should only have shared pages migrated, or that should not be migrated (e. g. you don't want to migrate
/bin/cshall the time.)
Would the program header not be a better place? There are spare bits there, I believe, and then each PT_LOAD segment could have a different attribute, perhaps.
Signature · 2 lines
Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au The technical we do immediately, the political takes *forever*