I'm looking for a script or some other application that will use up a lot of memory on a Solaris or Linux server, in order to test a monitoring application. So far I have found a script that's good for CPU usage but it does nothing for memory. I have also tried the application called 'stress'... (0 Replies)
This is the code:
while test 1 -eq 1
do
read a
$a
if test $a = stop
then
break
fi
done
I read a command on every loop an execute it.
I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test.
For example echo hello.
Now the... (1 Reply)
Hi to all,
Recently i am testing an equipment that runs in i586 fedora linux. I have to test mmap function. For that i determined to fill the memory and run the required application to check whether it throws any mmap error regarding low resources.
This is the line that does the allocation. ... (3 Replies)
Hi
I have an integrity machine rx7620 and rx8640 running hp-ux 11.31. I'm planning to fine tune the system:
- I would like to know when does the memory swap space spill over to the device swap space?
- And how much % of memory swap utilization should be specified (swap space device... (6 Replies)
Please anyone can tell me what is Stress in unix and how can I Perform Stress Runs on the UNIX environment
Please reply soon it's urgent:confused: (5 Replies)
I need to find out if the NIC on my MP-RAS box is bad. Unfortunately just sending out a ping to the loop back is not going to cut it. I need to be able to send out packets of information for several minutes at a time. I can't seem to find a tool or command to do this. Is anyone aware of a way to... (1 Reply)
Hi there.
First things first, this is nothing to do with the internet or ISP speed, I know what that is, I know what it's doing.
I have a cluster of 128 single board computers running a branch of Debian. I want to run some kind of stress test to ensure they can transfer data (a) to each... (2 Replies)
Discussion started by: MuntyScrunt
2 Replies
LEARN ABOUT NETBSD
atomic_cas_ptr
ATOMIC_CAS(3) BSD Library Functions Manual ATOMIC_CAS(3)NAME
atomic_cas, atomic_cas_32, atomic_cas_uint, atomic_cas_ulong, atomic_cas_ptr, atomic_cas_64, atomic_cas_32_ni, atomic_cas_uint_ni,
atomic_cas_ulong_ni, atomic_cas_ptr_ni, atomic_cas_64_ni -- atomic compare-and-swap operations
SYNOPSIS
#include <sys/atomic.h>
uint32_t
atomic_cas_32(volatile uint32_t *ptr, uint32_t old, uint32_t new);
unsigned int
atomic_cas_uint(volatile unsigned int *ptr, unsigned int old, unsigned int new);
unsigned long
atomic_cas_ulong(volatile unsigned long *ptr, unsigned long old, unsigned long new);
void *
atomic_cas_ptr(volatile void *ptr, void *old, void *new);
uint64_t
atomic_cas_64(volatile uint64_t *ptr, uint64_t old, uint64_t new);
uint32_t
atomic_cas_32_ni(volatile uint32_t *ptr, uint32_t old, uint32_t new);
unsigned int
atomic_cas_uint_ni(volatile unsigned int *ptr, unsigned int old, unsigned int new);
unsigned long
atomic_cas_ulong_ni(volatile unsigned long *ptr, unsigned long old, unsigned long new);
void *
atomic_cas_ptr_ni(volatile void *ptr, void *old, void *new);
uint64_t
atomic_cas_64_ni(volatile uint64_t *ptr, uint64_t old, uint64_t new);
DESCRIPTION
The atomic_cas family of functions perform a compare-and-swap operation in an atomic fashion. The value of the variable referenced by ptr is
compared against old. If the values are equal, new is stored in the variable referenced by ptr.
The old value of the variable referenced by ptr is always returned regardless of whether or not the new value was stored. Applications can
test for success of the operation by comparing the return value to the value passed as old; if they are equal then the new value was stored.
The non-interlocked variants, *_ni(), guarantee atomicity within the same CPU with respect to interrupts and preemption. For example, they
are suitable for synchronizing compare-and-swap operations on a variable shared by a thread and an interrupt that are bound to the same CPU.
The *_ni() variants are not atomic with respect to different CPUs. *_ni() variants should avoid the interprocessor synchronization overhead
of the standard compare-and-swap operations.
The 64-bit variants of these functions are available only on platforms that can support atomic 64-bit memory access. Applications can check
for the availability of 64-bit atomic memory operations by testing if the pre-processor macro __HAVE_ATOMIC64_OPS is defined.
SEE ALSO atomic_ops(3)HISTORY
The atomic_cas functions first appeared in NetBSD 5.0.
NOTES
On some architectures, a *_ni() variant is merely an alias for the corresponding standard compare-and-swap operation. While the non-inter-
locked variant behaves correctly on those architectures, it does not avoid the interprocessor synchronization overhead.
BSD February 11, 2010 BSD