Sponsored Content
Top Forums Programming Synchronization Variable Storage Post 302572019 by Praveen_218 on Wednesday 9th of November 2011 02:36:50 AM
Old 11-09-2011
They are just variables (ofcourse the pthread lib treat them specially) so where ever you declare/define them there they’d appear; the only thing is their scope and visibility to pthreads that should guide you the location to declare them.

Like to add a quick-tip:
You can look at the process (having pid = x) memory area at /proc/<pid>/maps
Code:
cat /proc/x/maps

Gives you all *.so and other memory area of the process (in terms of memory ranges).

If you have to see the location of a perticular variable; just print it's address from your program and while the process is running, look at the location (find the range slab) where the address is falling. That is the location of your variable in the program. This is true for any address your program uses.

Thanks.
This User Gave Thanks to Praveen_218 For This Post:
 

3 More Discussions You Might Find Interesting

1. Programming

static variable storage

Hi, Where are the static variables actually stored in memory. Is it in .bss? In that case how is its storage different from global variables? From the ELF data is it possible to see the storage of different variables used in the program? eg: static int temp1; int gtemp1; main() {... (1 Reply)
Discussion started by: naan
1 Replies

2. Programming

Variable storage locations ...

I've got the following two queries: 1) What's the difference in performance if a variable storage is at bss and not at the data section (apart from the initialization to zero in case of data section variables --like static variables). In general, why a developer need to bother about the... (1 Reply)
Discussion started by: Praveen_218
1 Replies

3. Shell Programming and Scripting

Variable storage using awk

Hi, there is a file which contains some values in column format. I want to store those values in a variable.but when i am using awk it is storing all the values at a time. x=`awk '{print $1}' test2.txt` echo $x ab cd mn jk yt but i want the values to be stored one by one in that variable.... (3 Replies)
Discussion started by: arijitsaha
3 Replies
MIGRATEPAGES(8) 					   Linux Administrator's Manual 					   MIGRATEPAGES(8)

NAME
migratepages - Migrate the physical location a processes pages SYNOPSIS
migratepages pid from-nodes to-nodes DESCRIPTION
migratepages moves the physical location of a processes pages without any changes of the virtual address space of the process. Moving the pages allows one to change the distances of a process to its memory. Performance may be optimized by moving a processes pages to the node where it is executing. If multiple nodes are specified for from-nodes or to-nodes then an attempt is made to preserve the relative location of each page in each nodeset. For example if we move from nodes 2-5 to 7,9,12-13 then the preferred mode of operation is to move pages from 2->7, 3->9, 4->12 and 5->13. However, this is only posssible if enough memory is available. Valid node specifiers all All nodes number Node number number1{,number2} Node number1 and Node number2 number1-number2 Nodes from number1 to number2 ! nodes Invert selection of the following specification. NOTES
Requires an NUMA policy aware kernel with support for page migration (linux 2.6.16 and later). migratepages will only move pages that are not shared with other processes if called by a user without administrative priviledges (but with the right to modify the process). migratepages will move all pages if invoked from root (or a user with administrative priviledges). FILES
/proc/<pid>/numa_maps for information about the NUMA memory use of a process. COPYRIGHT
Copyright 2005-2006 Christoph Lameter, Silicon Graphics, Inc. migratepages is under the GNU General Public License, v.2 SEE ALSO
numactl(8) , set_mempolicy(2) , get_mempolicy(2) , mbind(2) , sched_setaffinity(2) , sched_getaffinity(2) , proc(5) , ftok(3) , shmat(2) , taskset(1) SGI
Jan 2005 MIGRATEPAGES(8)
All times are GMT -4. The time now is 05:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy