Sponsored Content
Operating Systems Solaris Application running too slow on Sun SPARC T5440 but run normal on sun M3000 Post 302655575 by hergp on Wednesday 13th of June 2012 10:53:54 AM
Old 06-13-2012
I am not aware of any way to combine the computing power of several cores for one single thread, it's just how the CPU is designed.
This User Gave Thanks to hergp For This Post:
 

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
unix_master(9r) 														   unix_master(9r)

NAME
unix_master - General: Forces execution onto the master CPU SYNOPSIS
void unix_master( void ); ARGUMENTS
None DESCRIPTION
The unix_master routine forces execution of the kernel thread onto the master CPU (also called the boot CPU). In other words, unix_master binds the kernel thread to the master CPU. To release the kernel thread from the bind to the master CPU, call the unix_release routine. You can make recursive calls to unix_master as long as you make an equal number of calls to unix_release. The unix_master routine provides another way besides the simple and complex lock routines to make a kernel module symmetric multiprocessing (SMP) safe. Although calling unix_master is not optimal for performance on an SMP CPU, it does provide third-party kernel module writers with an easy way to make their modules SMP safe without using the lock routines. NOTES
Device drivers should not directly call the unix_master and unix_release routines. One exception to this recommendation is when you want a device driver's kernel threads to run only on the master CPU. This situation occurs when your driver creates and starts its own kernel threads and you set the d_funnel member of the associated dsent structure to the value DEV_FUNNEL. In this case, each kernel thread must call unix_master once to ensure that the kernel thread runs only on the master CPU. Remember to make a corresponding call to unix_release. CAUTIONS
To avoid deadlock, do not call the unix_master routine under the following circumstances: When holding a simple lock In the driver's inter- rupt service routine RETURN VALUES
None SEE ALSO
routines: unix_release(9r) unix_master(9r)
All times are GMT -4. The time now is 09:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy