06-10-2014
Can you disable CPUs and/or hyperthreading as necessary via BIOS settings on your new hardware to limit the OS to only one CPU thread? That seems to me to be a really easy test to run that will provide good information.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
What is the SMP support like when you are running Linux 7.3 on a system with 2-4 CPUs? (3 Replies)
Discussion started by: AngryRabbi
3 Replies
2. SCO
I have a dell machine Dell 2600 PowerEdge it has two processor (intel Xeon ).
Is there a path or a software that will work with SCO unix in order to enable second processor and how would i know that the second processor is active.
Thanks a lot guys . (1 Reply)
Discussion started by: josramon
1 Replies
3. Linux Benchmarks
System:
CPU/Speed: Dual Intel Xeon 2.4Ghz
Ram: 2 GB DDR 266 SDRAM
Motherboard: SuperMicro X5DE8-GG
Bus: 533MHz/400MHz system bus -
Cache: 512KB
HD Controller: EIDE Serverworks™ GC-SL Chipset
Extra GCC compiler flags:
-s... (3 Replies)
Discussion started by: Neo
3 Replies
4. Red Hat
I have installed redhat linux 9.0 on P4 HT machine. The grub boot loader shows path to smp mode and normal mode. when machine shut downs from smp version kernal , need to press the power button to power off. But in normal mode the system shut downs or power downs automatically(ie, full... (2 Replies)
Discussion started by: pcsaji
2 Replies
5. Programming
Interesting issue. There was some discussion on the LKML last year regarding the potential problems in concurrent applications reusing file descriptors in various scenarios. The main issue is that the reuse of a file descriptor and reception of data in a threaded application can be confused pretty... (1 Reply)
Discussion started by: ramen_noodle
1 Replies
6. UNIX for Advanced & Expert Users
I compiled my device driver with the profiling option -p but while linking I am getting undefined reference to _mcount.
LD /vobs/femto_drivers/DspBiosLink/dsplinkk/src/dsplinkk.o
Building modules, stage 2.
MODPOST
*** Warning: "_mcount" undefined!
Architechture: ppc32
From... (0 Replies)
Discussion started by: Ashok V
0 Replies
7. High Performance Computing
Hola, he instalado mpich2 vs. 1.2.1p1 en un cluster de biprocesadores con las opciones por defecto (antes usaba ssm pero visto que se quedaba colgado, lo he dejado con nemesis).
El caso es que quisiera que cada vez que lanzo un job (por ejemplo de 2 procesos), cada proceso del trabajo se fuera... (1 Reply)
Discussion started by: Sonia_
1 Replies
8. UNIX for Dummies Questions & Answers
question goes like this :
Explain how users can profile execution of a process with help of an example?
can some one pls give me the answer?? (1 Reply)
Discussion started by: rakesh1988
1 Replies
9. AIX
Hello everybody,
Please let me know if there are any free C profiling tool for AIX environment
Thanks in advance (0 Replies)
Discussion started by: SteAlma
0 Replies
10. Debian
I was wondering how can I find the culprit of a slow shutdown on my debian box? I am actually looking for a diagnosis tool that might dump the process name and amount of time it took to close the process after signal was send.
As for now I am trying to use journalctl to seek some information,... (5 Replies)
Discussion started by: Varun Pandey
5 Replies
LEARN ABOUT SUSE
smp_rep_manufacturer
SMP_REP_MANUFACTURER(8) SMP_UTILS SMP_REP_MANUFACTURER(8)
NAME
smp_rep_manufacturer - invoke REPORT MANUFACTURER INFORMATION SMP function
SYNOPSIS
smp_rep_manufacturer [--help] [--hex] [--interface=PARAMS] [--raw] [--sa=SAS_ADDR] [--verbose] [--version] SMP_DEVICE[,N]
DESCRIPTION
Sends a SAS Management Protocol (SMP) REPORT MANUFACTURER INFORMATION request function to a SMP target. The SMP target is identified by the
SMP_DEVICE and the SAS_ADDR. Depending on the interface, the SAS_ADDR may be deduced from the SMP_DEVICE. With one interface there is one
SMP_DEVICE per machine so the SMP_DEVICE,N syntax is needed to differentiate between HBAs if there are multiple present.
OPTIONS
Mandatory arguments to long options are mandatory for short options as well.
-h, --help
output the usage message then exit.
-H, --hex
output the response in hexadecimal.
-I, --interface=PARAMS
interface specific parameters. In this case "interface" refers to the path through the operating system to the SMP initiator. See
the smp_utils man page for more information.
-r, --raw
send the response to stdout in binary. All error messages are sent to stderr.
-s, --sa=SAS_ADDR
specifies the SAS address of the SMP target device. Typically this is an expander. This option may not be needed if the SMP_DEVICE
has the target's SAS address within it. The SAS_ADDR is in decimal but most SAS addresses are shown in hexadecimal. To give a number
in hexadecimal either prefix it with '0x' or put a trailing 'h' on it.
-v, --verbose
increase the verbosity of the output. Can be used multiple times
-V, --version
print the version string and then exit.
CONFORMING TO
The SMP REPORT MANUFACTURER function was introduced in SAS-1, with small additions in SAS-1.1 .
AUTHORS
Written by Douglas Gilbert.
REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>.
COPYRIGHT
Copyright (C) 2006-2008 Douglas Gilbert
This software is distributed under a FreeBSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR-
POSE.
SEE ALSO
smp_utils, smp_discover(smp_utils)
smp_utils-0.93 January 2008 SMP_REP_MANUFACTURER(8)