Sponsored Content
Full Discussion: Heart OS and Love OS?
Top Forums UNIX for Dummies Questions & Answers Heart OS and Love OS? Post 302550802 by frank_rizzo on Saturday 27th of August 2011 01:42:59 PM
Old 08-27-2011
been using UNIX for a long time and have never heard of such a thing
 

3 More Discussions You Might Find Interesting

1. AIX

POWER HA 5.5 & Service IP / disk heart beat

Hello, I have a quick question regarding POWER HA ( HACMP ) 5.5 ; I have four ethernet adapters en0 en1 en2 en3 en0 is configured as BOOT_IP with IP address all other ethernet adapters are empty en1 / en2 / en3 so when I configure the service IP and start HACMP , the service IP... (2 Replies)
Discussion started by: filosophizer
2 Replies

2. What is on Your Mind?

Heart beat monitor using android

I just had this idea of using Android (a linux derivative) to monitor heart rates of patients with a history of cardiac problems. There are plenty apps around that monitor heart rates, but none for people that require medical attention when their heart rate drops below a certain level for more... (0 Replies)
Discussion started by: figaro
0 Replies

3. Red Hat

configuring broadcast traffic to heart commuication RH cluster

Hello, can someone please suggest how do I configure heartbeat communication to user broadcasting instead of multicasting for redhat cluster setup. Thanks, (3 Replies)
Discussion started by: bobby320
3 Replies
TASKSET(1)							   User Commands							TASKSET(1)

NAME
taskset - set or retrieve a process's CPU affinity SYNOPSIS
taskset [options] mask command [argument...] taskset [options] -p [mask] pid DESCRIPTION
taskset is used to set or retrieve the CPU affinity of a running process given its pid, or to launch a new command with a given CPU affin- ity. CPU affinity is a scheduler property that "bonds" a process to a given set of CPUs on the system. The Linux scheduler will honor the given CPU affinity and the process will not run on any other CPUs. Note that the Linux scheduler also supports natural CPU affinity: the scheduler attempts to keep processes on the same CPU as long as practical for performance reasons. Therefore, forcing a specific CPU affinity is useful only in certain applications. The CPU affinity is represented as a bitmask, with the lowest order bit corresponding to the first logical CPU and the highest order bit corresponding to the last logical CPU. Not all CPUs may exist on a given system but a mask may specify more CPUs than are present. A retrieved mask will reflect only the bits that correspond to CPUs physically on the system. If an invalid mask is given (i.e., one that corresponds to no valid CPUs on the current system) an error is returned. The masks may be specified in hexadecimal (with or without a leading "0x"), or as a CPU list with the --cpu-list option. For example, 0x00000001 is processor #0, 0x00000003 is processors #0 and #1, 0xFFFFFFFF is processors #0 through #31, 32 is processors #1, #4, and #5, --cpu-list 0-2,6 is processors #0, #1, #2, and #6. When taskset returns, it is guaranteed that the given program has been scheduled to a legal CPU. OPTIONS
-a, --all-tasks Set or retrieve the CPU affinity of all the tasks (threads) for a given PID. -c, --cpu-list Interpret mask as numerical list of processors instead of a bitmask. Numbers are separated by commas and may include ranges. For example: 0,5,8-11. -p, --pid Operate on an existing PID and do not launch a new task. -V, --version Display version information and exit. -h, --help Display help text and exit. USAGE
The default behavior is to run a new command with a given affinity mask: taskset mask command [arguments] You can also retrieve the CPU affinity of an existing task: taskset -p pid Or set it: taskset -p mask pid PERMISSIONS
A user can change the CPU affinity of a process belonging to the same user. A user must possess CAP_SYS_NICE to change the CPU affinity of a process belonging to another user. A user can retrieve the affinity mask of any process. SEE ALSO
chrt(1), nice(1), renice(1), sched_getaffinity(2), sched_setaffinity(2) See sched(7) for a description of the Linux scheduling scheme. AUTHOR
Written by Robert M. Love. COPYRIGHT
Copyright (C) 2004 Robert M. Love. This is free software; see the source for copying conditions. There is NO warranty; not even for MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. AVAILABILITY
The taskset command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/. util-linux August 2014 TASKSET(1)
All times are GMT -4. The time now is 02:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy