Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Please Stay Home and Safe During the Pandemic Post 303045445 by 000vikas on Tuesday 24th of March 2020 01:34:13 AM
Old 03-24-2020
Thank you and you too!
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

What can I do,if I want windows me and unix stay in the same computer?

My computer's operating system is windows me,now.I want install unix in it while I don't want to kill the windows me.So could u tell me what to do?I'd like you give me detailed information about it.Thank u. (2 Replies)
Discussion started by: David
2 Replies

2. UNIX for Dummies Questions & Answers

Unix server will not stay up on the network

:mad: Hello, I am a beginner at UNIX. I have a server running SCO UNIXWARE 7.1.0 Every morning this week the server has been down. I have to Hardboot her to get her back online. What commands can I do to help me diagnose what is going on? This is urgent....thank you. (3 Replies)
Discussion started by: jback
3 Replies

3. Shell Programming and Scripting

How does the environment stay set

I am running this pre-script with a post scripts that needs to share the same variables. How do I keep the environment variable settings for the next script to access from the RMAN Script? Prescript #1 #RMAN Script #!/bin/ksh ORACLE_SID=INVPRD;export ORACLE_SID... (1 Reply)
Discussion started by: gzs553
1 Replies

4. Solaris

Async-Signal-Safe versus MT-Safe

Hi, I am Solaris 9 developer and notice that the documentation does not provide a clear notion of the inherent concurrency in routines defined as "Async-Signal-Safe". Routines defined as "MT-Safe" obviously have the best level of concurrency, compared to normal "Safe" interfaces. I have... (1 Reply)
Discussion started by: tristan12
1 Replies

5. UNIX for Dummies Questions & Answers

how to break within a case/esac and stay in script

Wrote the following loop to but if I use exit, then I break entirely from my script, but instead I want to break from the case/esac and go to the next line in my script. I guess I need to know how to exit gracefully from a "while (true). Also, how can I allow the user to enter upper or lowercase... (4 Replies)
Discussion started by: tumblez
4 Replies

6. AIX

xntpd won't stay up...

AIX 5.3-5300.09.06.1013 (AIX 5.3 TL9 SP6) # startsrc -s xntpd -a "-x" (with -x at the end of the xntpd line in /etc/rc.tcpip, too.) will run for 5-15 minutes, and then die. # errpt -a with a search on xntpd gives me this: ------------------------------------------------ LABEL: ... (7 Replies)
Discussion started by: dafydd2277
7 Replies

7. Shell Programming and Scripting

cp -p /home/* home/exp/*.date not working please help

:( ---------- Post updated at 01:51 AM ---------- Previous update was at 01:50 AM ---------- Not working ---------- Post updated at 02:04 AM ---------- Previous update was at 01:51 AM ---------- cp -p /home/* home/exp/*.`date` i am using this (4 Replies)
Discussion started by: rishiraaz
4 Replies
GET_MEMPOLICY(2)					     Linux Programmer's Manual						  GET_MEMPOLICY(2)

NAME
get_mempolicy - Retrieve NUMA memory policy for a process SYNOPSIS
#include <numaif.h> int get_mempolicy(int *mode, unsigned long *nodemask, unsigned long maxnode, unsigned long addr, unsigned long flags); Link with -lnuma. DESCRIPTION
get_mempolicy() retrieves the NUMA policy of the calling process or of a memory address, depending on the setting of flags. A NUMA machine has different memory controllers with different distances to specific CPUs. The memory policy defines from which node mem- ory is allocated for the process. If flags is specified as 0, then information about the calling process's default policy (as set by set_mempolicy(2)) is returned. The pol- icy returned [mode and nodemask] may be used to restore the process's policy to its state at the time of the call to get_mempolicy() using set_mempolicy(2). If flags specifies MPOL_F_MEMS_ALLOWED (available since Linux 2.6.24), the mode argument is ignored and the set of nodes [memories] that the process is allowed to specify in subsequent calls to mbind(2) or set_mempolicy(2) [in the absense of any mode flags] is returned in nodemask. It is not permitted to combine MPOL_F_MEMS_ALLOWED with either MPOL_F_ADDR or MPOL_F_NODE. If flags specifies MPOL_F_ADDR, then information is returned about the policy governing the memory address given in addr. This policy may be different from the process's default policy if mbind(2) or one of the helper functions described in numa(3) has been used to establish a policy for the memory range containing addr. If the mode argument is not NULL, then get_mempolicy() will store the policy mode and any optional mode flags of the requested NUMA policy in the location pointed to by this argument. If nodemask is not NULL, then the nodemask associated with the policy will be stored in the location pointed to by this argument. maxnode specifies the number of node IDs that can be stored into nodemask--that is, the maximum node ID plus one. The value specified by maxnode is always rounded to a multiple of sizeof(unsigned long). If flags specifies both MPOL_F_NODE and MPOL_F_ADDR, get_mempolicy() will return the node ID of the node on which the address addr is allo- cated into the location pointed to by mode. If no page has yet been allocated for the specified address, get_mempolicy() will allocate a page as if the process had performed a read [load] access to that address, and return the ID of the node where that page was allocated. If flags specifies MPOL_F_NODE, but not MPOL_F_ADDR, and the process's current policy is MPOL_INTERLEAVE, then get_mempolicy() will return in the location pointed to by a non-NULL mode argument, the node ID of the next node that will be used for interleaving of internal kernel pages allocated on behalf of the process. These allocations include pages for memory mapped files in process memory ranges mapped using the mmap(2) call with the MAP_PRIVATE flag for read accesses, and in memory ranges mapped with the MAP_SHARED flag for all accesses. Other flag values are reserved. For an overview of the possible policies see set_mempolicy(2). RETURN VALUE
On success, get_mempolicy() returns 0; on error, -1 is returned and errno is set to indicate the error. ERRORS
EFAULT Part of all of the memory range specified by nodemask and maxnode points outside your accessible address space. EINVAL The value specified by maxnode is less than the number of node IDs supported by the system. Or flags specified values other than MPOL_F_NODE or MPOL_F_ADDR; or flags specified MPOL_F_ADDR and addr is NULL, or flags did not specify MPOL_F_ADDR and addr is not NULL. Or, flags specified MPOL_F_NODE but not MPOL_F_ADDR and the current process policy is not MPOL_INTERLEAVE. Or, flags speci- fied MPOL_F_MEMS_ALLOWED with either MPOL_F_ADDR or MPOL_F_NODE. (And there are other EINVAL cases.) VERSIONS
The get_mempolicy() system call was added to the Linux kernel in version 2.6.7. CONFORMING TO
This system call is Linux-specific. NOTES
For information on library support, see numa(7). SEE ALSO
getcpu(2), mbind(2), mmap(2), set_mempolicy(2), numa(3), numa(7), numactl(8) COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2008-08-15 GET_MEMPOLICY(2)
All times are GMT -4. The time now is 03:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy