Sponsored Content
Operating Systems Solaris Application running too slow on Sun SPARC T5440 but run normal on sun M3000 Post 302655523 by insatiable1610 on Wednesday 13th of June 2012 09:48:04 AM
Old 06-13-2012
My application is a third-party application so i can't change, please help me find any process, thread or commands of OS in my application using a lot of computing power on thread . I can request my software vendors to review it.
Many thanks for your help.

Last edited by insatiable1610; 06-13-2012 at 09:54 PM..
 

7 More Discussions You Might Find Interesting

1. Solaris

Difference between sun sparc 32-bit and sun sparc 64-bit

Hi , could you please clarify me the difference between sun sparc 32-bit and sun sparc 64-bit? means on which processors these are supporting (pentium processors, sun sparc processors) Regards, Rajesh (1 Reply)
Discussion started by: pmrajesh21
1 Replies

2. High Performance Computing

Normal (not crossover) cable for Sun cluster interconnect..

Hi grus, has anybody tried for Sun cluster interconnect normal cable ,, I mean not interconnect .. What do u think ..does it support this ? Not long ago I tried Veritas cluster and its interconnections work great with normal cable .. I wonder what will Sun cluster say to it :)) (3 Replies)
Discussion started by: samar
3 Replies

3. Solaris

SUN T5240 vs M3000

Hi, We are planning to buy new server for our data center. Sun T5240 or M3000 which one have better performance, we are going to create many dt sessions in this server. So, i need your suggestions. RJS (4 Replies)
Discussion started by: rajasekg
4 Replies

4. Solaris

Adding new hard drives on Sun SPARC T5440 server with Solaris 10

I need to add two new hard drives of 300 GB capacity to a SunSPARC T5440 server. The server currently has two hard drives of 146 GB each. How do I add the new drives to the existing UFS? What are the procedures involved in setting this server with the new hard drives? I am very new to Solaris... (6 Replies)
Discussion started by: ramatnmcc
6 Replies

5. Solaris

Usb driver update on Sun T5440

I need a help to find the patch for solaris to fix USB drivers issue on Solaris 10. The server has a PCIE card which is not recognised by the OS. I run #fmadm faulty command which report issue and recommandation to apply the new patch. I got a reference to //sun.com/msg/PCIEX-8000-6D but... (0 Replies)
Discussion started by: espengongo
0 Replies

6. Emergency UNIX and Linux Support

disk replacment, SUN M3000

we have a SUN M3000 server. setup as only 1 domain. disk c0t0d0 and c0t1d0 and setup as SVM mirrors. a few days ago disk T1 failed. new we have replaced the disk, but can's see the disk in format. have done cfgadm and devfsadm. still can't access the new disk in format. the output... (6 Replies)
Discussion started by: robsonde
6 Replies

7. UNIX for Beginners Questions & Answers

Start /SYS on SUN SPARC does not start machine [SUN SPARC ENTERPRISE T-5240]

-> start /SYS Are you sure you want to start /SYS (y/n)? y Starting /SYS ]-> show HOST /HOST Targets: bootmode diag domain Properties: autorestart = reset autorunonerror = false bootfailrecovery = poweroff ... (29 Replies)
Discussion started by: z_haseeb
29 Replies
thr_exit(3C)						   Standard C Library Functions 					      thr_exit(3C)

NAME
thr_exit - terminate the calling thread SYNOPSIS
cc -mt [ flag... ] file...[ library... ] #include <thread.h> void thr_exit(void *status); DESCRIPTION
The thr_exit() function terminates the calling thread, in a similar way that exit(3C) terminates the calling process. If the calling thread is not detached, then the thread's ID and the exit status specified by status are retained. The value status is then made available to any successful join with the terminating thread (see thr_join(3C)); otherwise, status is disregarded allowing the thread's ID to be reclaimed immediately. Any cancellation cleanup handlers that have been pushed and not yet popped are popped in the reverse order that they were pushed and then executed. After all cancellation cleanup handlers have been executed, if the thread has any thread-specific data, appropriate destructor functions will be called in an unspecified order. Thread termination does not release any application visible process resources,including, but not limited to, mutexes and file descriptors, nor does it perform any process level cleanup actions, including, but not limited to, calling any atexit() routines that might exist. If any thread, including the main() thread, calls thr_exit(), only that thread will exit. If main() returns or exits (either implicitly or explicitly), or any thread explicitly calls exit(), the entire process will exit. The behavior of thr_exit() is undefined if called from a cancellation cleanup handler or destructor function that was invoked as a result of either an implicit or explicit call to thr_exit(). After a thread has terminated, the result of access to local (auto) variables of the thread is undefined. Thus, references to local vari- ables of the exiting thread should not be used for the thr_exit() status parameter value. If any thread (except the main() thread) implicitly or explicitly returns, the result is the same as if the thread called thr_exit() and it will return the value of status as the exit code. The process will terminate with an exit status of 0 after the last non-daemon thread has terminated (including the main() thread). This behavior is the same as if the application had called exit() with a 0 argument at thread termination time. RETURN VALUES
The thr_exit() function cannot return to its caller. ERRORS
No errors are defined. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ SEE ALSO
exit(3C), thr_create(3C), thr_join(3C), thr_keycreate(3C), attributes(5), standards(5) NOTES
Although only POSIX implements cancellation, cancellation can be used with Solaris threads, due to their interoperability. The status argument should not reference any variables local to the calling thread. SunOS 5.10 27 Mar 2000 thr_exit(3C)
All times are GMT -4. The time now is 10:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy