Sponsored Content
Full Discussion: Solaris SPARC speed issue
Operating Systems Solaris Solaris SPARC speed issue Post 302698705 by Pug on Monday 10th of September 2012 06:40:33 PM
Old 09-10-2012
Again, thank you for your responses.

So please let me clarify a few points to be sure.

1. 'hergp' is saying that if the issue is that they are using a T1 T2 type multi core SPARC than the issue is not so much the 32 vs 64 bit compile as it is the single threaded vs multi-threaded processing. Correct?
On Windows x86 vs X64 we found that the increase in compiling to X64 is just under 20% (comparing the running of one process on the same input data). Would you expect something similar on SPARC?

2. 'jlliagreis' saying that if it is possible to design our program to be multi-threaded (which I don't think we can) or if we run the program in parallel processes on different sets of data instead of in sequence, then we should be able to see some improvement. However, the amount will depend on the type of bottle neck we are experiencing (which we do not know yet). So for example, if it is straight CPU bound then we should see the best improvement, whereas if it is I/O bound then they may be less improvement, etc.

3. How do I know if we are running T1 or T2 with regard to floating point? I noticed that you said it is niagara based on the sun4v. How do I tell what T level they have?

4. What Solaris SPARC hardware would be better for doing this type of processing? I am not sure we have a choice but I am certainly curious.

---------- Post updated at 04:40 PM ---------- Previous update was at 09:38 AM ----------

One other things. They have two servers. One is a T2 and the other a T3 and specifically they are:SunOS 5.10 Generic_147440-09 sun4u sparc SUNW,Sun-Fire-V245 (T2)
SunOS 5.10 Generic_147440-01 sun4v sparc sun4v (T3)

What does this tell us about single thread / multi-thread or floating point etc?
How does sun4v differ from sun4u? How does T2 differ from T3?

Thank you.
 

8 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

Issue with installing solaris 10 OS on sparc 5

Rebooting with command: boot cdrom -s Boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f File and args: -s Evaluating: boot cdrom -s Can't open boot device If any one knows please advise. I have changed the CDrom but it did not help. (1 Reply)
Discussion started by: ark
1 Replies

2. UNIX for Dummies Questions & Answers

Running Solaris Sparc Apps on X86 Solaris

I know that Sun make s a version of Solaris for Sparc platforms and also an x86 (Intel/AMD) release of Solaris. Can an application that runs on Solaris/Sparc also run on a PC running the x86 release of Solaris? Would a different release be required or any re-compling of the application? jim (1 Reply)
Discussion started by: stocksj
1 Replies

3. Solaris

CC 5.5 compiler flag to issue 64bit porting warnings on sparc-solaris

Hi, We are porting our application from 32bit to 64bit. We tried -xarch=v9, -xarc=v9a and -xport64=full options so that compiler to issue 64bit porting warnings. But we are not getting any porting warninings WE are using CC 5.5 compiler on sparc-solaris m/c. Please tell us some powerful... (0 Replies)
Discussion started by: shobhah
0 Replies

4. Solaris

Issue while installing: Solaris 10 SPARC Recommended Patch Cluster (2009.10.23)

Hello, As explained, I've encountered an issue while installing Solaris 10 SPARC Recommended Patch Cluster (2009.10.23). Actually, patch no 120011-14 stops with the following error: ERROR: attribute verification of </var/run/.patchSafeMode/root/usr/bin/passwd> failed file type <f>... (6 Replies)
Discussion started by: a.mauger
6 Replies

5. Infrastructure Monitoring

Nagios on Solaris 10 Sparc issue

I've got it installed but when I logging to the interface to http://localhost/nagios I get the following: Forbidden You don't have permission to access /nagios/ on this server. Apache/2.0.63 (Unix) DAV/2 Server at localhost Port 80 im running Solaris Version: SunOS dotstoas442 5.10... (0 Replies)
Discussion started by: frenchykd
0 Replies

6. Solaris

hba speed Solaris 9

Hello, In Solaris 10 I can use fcinfo to find what speed the hba ports are running at, am I able to find this out using Solaris 9? I have tried a few variations on luxadm but cant find anything relevant. Thanks. (1 Reply)
Discussion started by: Actuator
1 Replies

7. UNIX for Dummies Questions & Answers

can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC?

Hi Gurus can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC? regards, Israel. (9 Replies)
Discussion started by: iga3725
9 Replies

8. Solaris

How to read this Solaris version:-Solaris 8 HW 5/03 s28s_hw2wos_06a SPARC?

Hi Guys, Could you please tell me how to read this Solaris version:- Solaris 8 HW 5/03 s28s_hw2wos_06a SPARC Thanks. (3 Replies)
Discussion started by: manalisharmabe
3 Replies
as(1)								   User Commands							     as(1)

NAME
as - assembler SYNOPSIS
SPARC as [-b] [-i] [-K {pic,PIC}] [-L] [-m] [-n] [-o outfile] [-P] [-Dname] [-Dname=def] [-Ipath] [-Uname]... [-q] [-Qy | n] [-s] [-S [a | b | c | l | A | B | C | L]] [-T] [-V] [-xarch=v7 | -xarch=v8 | -xarch=v8a | -xarch=v8plus | -xarch=v8plusa | -xarch=v8plusb | -xarch=v8plusd | -xarch=v8plusv | -xarch=v9 | -xarch=v9a | -xarch=v9b | -xarch=v9d | -xarch=v9v] [-xF] [-Y dirname] filename... x86 as [-b] [-i] [-K PIC] [-L] [-m] [-n] [-o outfile] [-P] [-Dname] [-Dname=def] [-Ipath] [-Uname]... [-Qy | n] [-s] [-S [a | b | c | l | A | B | C | L]] [-T] [-V] [-xarch=generic64 | -xarch=amd64] [-Y dirname] [-xmodel= [ SMALL | KERNEL ]] filename... DESCRIPTION
The as command creates object files from assembly language source files. OPTIONS
Common Options The following flags are common to both SPARC and x86. They can be specified in any order: -b Generates extra symbol table information. -i Ignore line number information from preprocessor. -K pic | PIC Generates position-independent code. -L Saves all symbols, including temporary labels that are normally discarded to save space, in the ELF symbol table. -m Runs the m4(1) macro processor on the input to the assembler. -n Suppresses all the warnings while assembling. -o outfile Puts the output of the assembly in outfile. By default, the output file name is formed by removing the .s suffix, if there is one, from the input file name and appending a .o suffix. -P Runs cpp(1), the C preprocessor, on the files being assembled. The preprocessor is run separately on each input file, not on their concatenation. The preprocessor output is passed to the assembler. -Dname When the -P option is in effect, these options are passed to the cpp(1) preprocessor without interpretation by the -Dname=def as command; otherwise, they are ignored. -Ipath When the -P option is in effect, this option is passed to the cpp(1) preprocessor without interpretation by the as command; otherwise, it is ignored. -Uname When the -P option is in effect, this option is passed to the cpp(1) preprocessor without interpretation by the as command; otherwise, it is ignored. -Qy | n If y is specified, this option produces the assembler version information in the comment section of the output object file. If n is specified, the information is suppressed. -s Places all stabs in the .stabs section. By default, stabs are placed in stabs.excl sections, which are stripped out by the static linker, ld(1), during final execution. When the -s option is used, stabs remain in the final exe- cutable because .stab sections are not stripped by the static linker. -S[a|b|c|l|A|B|C|L] Produces a disassembly of the emitted code to the standard output. Adding each of the following characters to the -S option produces: a disassembling with address b disassembling with ".bof" c disassembling with comments l disassembling with line numbers Capital letters turn the switch off for the corresponding option. -T This is a migration option for 4.x assembly files to be assembled on 5.x systems. With this option, the symbol names in 4.x assembly files are interpreted as 5.x symbol names. -V Writes the version number of the assembler being run on the standard error output. -xF Allows function reordering by the Performance Analyzer. If you compile with the -xF option, and then run the Perfor- mance Analyzer, you can generate a map file that shows an optimized order for the functions. The subsequent link to build the executable file can be directed to use that map file by using the linker -M mapfile option. It places each function from the executable file into a separate section. -Y dirname Specify directory m4 and/or cm4def. Options for SPARC only -q Performs a quick assembly. When the -q option is used, many error checks are not performed. This option disables many error checks. Use of this option to assemble handwritten assembly language is not recommended. -xarch=v7 This option instructs the assembler to accept instructions defined in the SPARC version 7 (V7) architecture. The result- ing object code is in ELF format. -xarch=v8 This option instructs the assembler to accept instructions defined in the SPARC-V8 architecture, less the quad-precision floating-point instructions. The resulting object code is in ELF format. -xarch=v8a This option instructs the assembler to accept instructions defined in the SPARC-V8 architecture, less the quad-precision floating-point instructions and less the fsmuld instruction. The resulting object code is in ELF format. This is the default choice of the -xarch=options. -xarch=v8plus This option instructs the assembler to accept instructions defined in the SPARC-V9 architecture, less the quad-precision floating-point instructions. The resulting object code is in ELF format. It does not execute on a Solaris V8 system (a machine with a V8 processor). It executes on a Solaris V8+ system. This combination is a SPARC 64-bit processor and a 32-bit OS. -xarch=v8plusa This option instructs the assembler to accept instructions defined in the SPARC-V9 architecture, less the quad-precision floating-point instructions, plus the instructions in the Visual Instruction Set (VIS). The resulting object code is in V8+ ELF format. It does not execute on a Solaris V8 system (a machine with a V8 processor). It executes on a Solaris V8+ system -xarch=v8plusb This option enables the assembler to accept instructions defined in the SPARC-V9 architecture, plus the instructions in the Visual Instruction Set (VIS), with UltraSPARC-III extensions. The resulting object code is in V8+ ELF32 format. -xarch=v8plusd This option enables the assembler to accept instructions DEFIned in UltraSPARC Architecture 2009. The resulting object code is in V8+ ELF32 format. -xarch=v8plusv This option enables the assembler to accept instructions defined in UltraSPARC Architecture 2005, including the exten- sions dealing with the sun4v virtual machine model. The resulting object code is in V8+ ELF32 format. -xarch=v9 This option limits the instruction set to the SPARC-V9 architecture. The resulting .o object files are in 64-bit ELF for- mat and can only be linked with other object files in the same format. The resulting executable can only be run on a 64-bit SPARC processor running 64-bit Solaris with the 64-bit kernel. -xarch=v9a This option limits the instruction set to the SPARC-V9 architecture, adding the Visual Instruction Set (VIS) and exten- sions specific to UltraSPARC processors. The resulting .o object files are in 64-bit ELF format and can only be linked with other object files in the same format. The resulting executable can only be run on a 64-bit SPARC processor running 64-bit Solaris with the 64-bit kernel. -xarch=v9b This option enables the assembler to accept instructions defined in the SPARC-V9 architecture, plus the Visual Instruc- tion Set (VIS), with UltraSPARC-III extensions. The resulting .o object files are in ELF64 format and can only be linked with other V9 object files in the same format. The resulting executable can only be run on a 64-bit processor running a 64-bit Solaris operating environment with the 64-bit kernel. -xarch=v9d This option enables the assembler to accept instructions defined in UltraSPARC Architecture 2009. The resulting object code is in ELF64 format. -xarch=v9v This option enables the assembler to accept instructions defined in UltraSPARC Architecture 2005, including the exten- sions dealing with the sun4v virtual machine model. The resulting object code is in ELF64 format. Options for x86 Only -xarch>=generic64 Limits the instruction set to AMD64. The resulting object code is in 64-bit ELF format. -xarch=amd64 Limits the instruction set to AMD64. The resulting object code is in 64-bit ELF format. -xmodel=[SMALL | KERNEL] For AMD64 only, generate R_X86_64_32S relocatable type for static data access under KERNEL. Otherwise, generate R_X86_64_32 under SMALL. SMALL is the default. OPERANDS
The following operand is supported: filename Assembly language source file ENVIRONMENT VARIABLES
TMPDIR The as command normally creates temporary files in the directory /tmp. Another directory can be specified by setting the environ- ment variable TMPDIR to the chosen directory. (If TMPDIR is not a valid directory, then as uses /tmp). FILES
By default, as creates its temporary files in /tmp. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsprot | +-----------------------------+-----------------------------+ SEE ALSO
cc(1B), cpp(1),ld(1), m4(1), nm(1), strip(1), tmpnam(3C), a.out(4), attributes(5) dbx and analyzer manual pages available with Sun Studio documentation. NOTES
If the -m option, which invokes the m4(1) macro processor, is used, keywords for m4 cannot be used as symbols (variables, functions, labels) in the input file, since m4 cannot determine which keywords are assembler symbols and which keywords are real m4 macros. Whenever possible, access the assembler through a compilation system interface program such as cc(1B). All undefined symbols are treated as global. SunOS 5.11 17 Mar 2008 as(1)
All times are GMT -4. The time now is 09:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy