Sponsored Content
Operating Systems Solaris Question: # of ldoms on T5240 with 2 T2 US 8 core Post 302862343 by bartus11 on Thursday 10th of October 2013 03:17:32 PM
Old 10-10-2013
"Theoretically" you could have more than 120 LDOMs (as your server has 128 processor threads), but performance on each of them would be very low.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

One Last Question about Core Files (distinguish) URGENT

now, what do you define as core files. there are some files outthere with the name perl.core, I-core.png, core.png I mean, are these classified as core files too??? i thought core files are simply files called "core". Please help me out this is urgent (2 Replies)
Discussion started by: TRUEST
2 Replies

2. Solaris

raidctl on SUN T5240

Setting up a T5240 with two disks c1t0d0 and c1t1d0. I am trying to use raidctl but when I issue. raidctl -l I get Controller 1 Disk: 0.0.0 Disk: 0.1.0 So I try raidctl -c '0.0.0 0.1.0' -r 1 1 and I get "Array in use." I try (4 Replies)
Discussion started by: photon
4 Replies

3. Solaris

cannot plumb nxge on T5240

its a fresh installation. during the OS setup, it did not prompt for IP, netmask and gateway. using Solaris 10 08/07 update 4. I tried to plumb manually but encountered no such interface error. but nxge interfaces can be greped from the /etc/path_to_inst file. getting similar error on... (3 Replies)
Discussion started by: incredible
3 Replies

4. 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

5. Solaris

ufsrestore T5240

Hi Friends we have sun T5240 server, we have taken ufsdump of this server remotely with scsi tapedrive, If we need to do ufsrestore means what we have to do, since T5240 has not having scsi port, any procedure is there? Regards Rajasekar (5 Replies)
Discussion started by: rajasekg
5 Replies

6. Solaris

Disable multithreading option on T5240

Hi Gurus Can any one tell me the process of disabling the multithreading option on T5240 server and my OS is on LDOM, having one physical processor with 8 core & 8 thread per core Regards (3 Replies)
Discussion started by: amity
3 Replies

7. Solaris

Cannot configure RAID on T5240

Hi ! I've been given a T5240 with 4 disks and 2 HBA cards (but no array connected). I did a factory reset on SP and NVRAM clean on OBP because the server had been used before. I boot cdrom in single mode and try to create a hw mirror with disks from c1... but only c2 is seen by raidctl. ... (2 Replies)
Discussion started by: delavega
2 Replies

8. Solaris

Reducing Cores in T5240 server for meeting Oracle Core Licences

Hi I need to reduce cores on T5240 server for meeting Oracle Core licenses. For that I have install the LDOM packages & run below mention commands. bash-3.2# ldm list-config factory-default config_initial bash-3.2# ldm set-vcpu 32 primary bash-3.2# ldm list-config... (5 Replies)
Discussion started by: amity
5 Replies

9. Solaris

Using a Modem on a T5-2 or a T5240

Hi Folks, Just a quick question - hopefully! I have an application currently running on a V890 with Solaris 9, I'd like to move this to either one of our T-5's or one of the T5240's in a Legacy container on an LDOM - but the fly in the ointment is the application still uses a standard Hayes... (3 Replies)
Discussion started by: gull04
3 Replies
pset_destroy(2) 						System Calls Manual						   pset_destroy(2)

NAME
pset_destroy() - destroy a processor set SYNOPSIS
DESCRIPTION
The function destroys the processor set pset, releasing all constituent processors and processes by default. The processors and processes are reassigned to the system default processor set. Once destroyed, the pset identifier becomes available for new processor sets that may be created in the future. The behavior when attempting to destroy a non-empty processor set may be controlled by changing the attribute of the processor set through the function. See pset_getattr(2). The following values are supported for the attribute: Reassign all processors in the pset to the system default processor set. Migrate all threads and processes bound to the pset to the system default proces- sor set. Make the request fail with if there are any threads or processes bound to pset or if there are processors assigned to the pset. Make the request fail with only if there are active threads or processes bound to the processor set. Otherwise, perform the operation by reassigning the processors in the pset to the system default processor set. If the threads and processes being reassigned to the default processor set have some binding to a processor or a locality domain in the pset being destroyed, their binding is reassigned to a processor or a locality domain in the system default processor set. A user with the privilege or a user with WRITE permission on the pset may destroy the processor set pset. The system default processor set may never be destroyed. Security Restrictions Some or all of the actions associated with this system call require the privilege. Processes owned by the superuser have this privilege. Processes owned by other users may have this privilege, depending on system configuration. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. Note on Logical Processor and Hyper-Threading Feature On systems with the Hyper-Threading (HT) feature enabled at the firmware level, each processor core may have more than one hyper-thread per physical processor core. Each hyper-thread is represented to the operating system and applications as a logical processor (LCPU). Due to the processor set contract, which specifies that applications bound to a processor set have complete and exclusive control of all processor cores within that processor set, migration of processors between two processor sets is done at the processor core granularity. For destruction of a processor set migrates a set of processor cores to the default processor set. Depending on the source processor set and the default processor set's the number of logical processors visible to the users and applications may change. EXAMPLES
Destroy a processor set with the processor set ID of pset. RETURN VALUE
returns zero on successful completion. Otherwise, -1 is returned and is set to indicate the error. ERRORS
fails if one or more of the following is true: The attribute value for the processor set does not allow deletion of a non-empty processor set. The operation was interrupted. pset is not a valid processor set. The processor set functionality is not supported by the underlying HP-UX version. The user does not have necessary permissions to destroy a processor set or the system default processor set was specified. SEE ALSO
psrset(1M), pset_assign(2), pset_bind(2), pset_create(2), pset_ctl(2), pset_getattr(2), privgrp(4), privileges(5). pset_destroy(2)
All times are GMT -4. The time now is 03:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy