Discussion of challenges involved in enabling legacy applications to scale on CMT architectures in particular and on multicore architectures in general. This SDN article also discusses possible architectural changes to the application.
Hi all,
Using shell script, how to assign tasks to individual processors in a multicore processor ? For example: If I have 4 processors, I want to give one job to each of the processors. (When I give multiple jobs, it's assigning all the load to a single processor. )
Thanks
R (5 Replies)
I'm fairly new to HP-UX, and I need to know how to identify the number of cores on a PA-8800 processor from the command line. Any help here would be appreciated. (11 Replies)
Everyone seemed to be a little stumped by the multicore question I asked earlier this week, so I decided I'd try a different angle.
Turns out that on a multicore system HP-UX reports every core as a seperate processor. All the usual commands (ioscan, top, etc.) report two processors for every... (7 Replies)
platform(n) Tcl Bundled Packages platform(n)
__________________________________________________________________________________________________________________________________________________NAME
platform - System identification support code and utilities
SYNOPSIS
package require platform ?1.0.4?
platform::generic
platform::identify
platform::patterns identifier
_________________________________________________________________DESCRIPTION
The platform package provides several utility commands useful for the identification of the architecture of a machine running Tcl.
Whilst Tcl provides the tcl_platform array for identifying the current architecture (in particular, the platform and machine elements) this
is not always sufficient. This is because (on Unix machines) tcl_platform reflects the values returned by the uname command and these are
not standardized across platforms and architectures. In addition, on at least one platform (AIX) the tcl_platform(machine) contains the CPU
serial number.
Consequently, individual applications need to manipulate the values in tcl_platform (along with the output of system specific utilities) -
which is both inconvenient for developers, and introduces the potential for inconsistencies in identifying architectures and in naming con-
ventions.
The platform package prevents such fragmentation - i.e., it establishes a standard naming convention for architectures running Tcl and
makes it more convenient for developers to identify the current architecture a Tcl program is running on.
COMMANDS
platform::identify
This command returns an identifier describing the platform the Tcl core is running on. The returned identifier has the general for-
mat OS-CPU. The OS part of the identifier may contain details like kernel version, libc version, etc., and this information may con-
tain dashes as well. The CPU part will not contain dashes, making the preceding dash the last dash in the result.
platform::generic
This command returns a simplified identifier describing the platform the Tcl core is running on. In contrast to platform::identify
it leaves out details like kernel version, libc version, etc. The returned identifier has the general format OS-CPU.
platform::patterns identifier
This command takes an identifier as returned by platform::identify and returns a list of identifiers describing compatible architec-
tures.
KEYWORDS
operating system, cpu architecture, platform, architecture
platform 1.0.4 platform(n)