Weird...
Handle 0x0700, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 32 kB
Maximum Size: 32 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: None
System Type: Data
Associativity: 8-way Set-associative
Handle 0x0701, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 4096 kB
Maximum Size: 4096 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: <OUT OF SPEC>
No idea which is referring to the empty socket and what the other one is...
Rob Marti
Systems Administrator
Sam Houston State University
936-294-3804 // rob@xxxxxxxx
-----Original Message-----
From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Broekman, Maarten
Sent: Tuesday, August 18, 2009 7:47 AM
To: General Red Hat Linux discussion list
Subject: RE: how to get the number of sockets
On the systems I have "Socket Designation" ends up only giving CPU sockets. A more contextual grep (or simply dumping it to more/less) might give more information about what it thinks is a "socket".
Maarten Broekman
> -----Original Message-----
> From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-
> bounces@xxxxxxxxxx] On Behalf Of Marti, Rob
> Sent: Tuesday, August 18, 2009 8:45 AM
> To: General Red Hat Linux discussion list
> Subject: RE: how to get the number of sockets
>
> My desktop's motherboard only has 2 sockets, but your command gives:
>
> [root@ab1-4-160 ~]# dmidecode | grep "Socket Designation"
> Socket Designation: CPU
> Socket Designation: Not Specified
> Socket Designation: Not Specified
>
> Not really sure that's accurate enough :) (and yeah I only have 1
socket
> filled... I feel like less of a man)
>
> Rob Marti
>
> -----Original Message-----
> From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list-
> bounces@xxxxxxxxxx] On Behalf Of Broekman, Maarten
> Sent: Tuesday, August 18, 2009 7:41 AM
> To: General Red Hat Linux discussion list
> Subject: RE: how to get the number of sockets
>
> /usr/sbin/dmidecode will give you similar information as well.
>
> # dmidecode | grep "Socket Designation"
> Socket Designation: Proc 1
> Socket Designation: Proc 2 ...
>
>
> Maarten Broekman
>
> > -----Original Message-----
> > From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list- >
> bounces@xxxxxxxxxx] On Behalf Of Marti, Rob > Sent: Tuesday, August
> 18, 2009 8:38 AM > To: General Red Hat Linux discussion list >
> Subject: RE: how to get the number of sockets > > Check
> manufacturers specs. There isn't a software way to check
for
> an
> > empty cpu - I'm guessing you meant empty because /proc/cpuinfo
tells
> you
> > how mant slots are full.
> >
> > grep physical /proc/cpuinfo | uniq -c
> > 4 physical id : 0
> > 4 physical id : 1
> >
> > So 4 cores on each of 2 sockets.
> >
> > Rob Marti
> > Systems Administrator
> > Sam Houston State University
> > 936-294-3804 // rob@xxxxxxxx
> >
> >
> > -----Original Message-----
> > From: redhat-list-bounces@xxxxxxxxxx [mailto:redhat-list- >
> bounces@xxxxxxxxxx] On Behalf Of ESGLinux > Sent: Tuesday, August
> 18, 2009 7:32 AM > To: General Red Hat Linux discussion list >
> Subject: how to get the number of sockets > > Hi all, > I was
> going to by a red hat license for a new server, an looking
the
> > note1 in this link:
> > https://www.redhat.com/apps/store/server/#note1
> >
> > I have reallized that the important thing is the number of
sockets,
> not
> > the number of cpus.
> >
> > So my question is simple, how can I get the number of sockets a >
> motherboard has, ?(without opening it. of coures) > > I have look
> at the /proc dir but I get only info about the cpus,
not
> > about the sockets,
> >
> > any suggestion,
> >
> > Thanks in advance
> >
> > ESG
> > --
> > redhat-list mailing list
> > unsubscribe
mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> > https://www.redhat.com/mailman/listinfo/redhat-list
> >
> > --
> > redhat-list mailing list
> > unsubscribe
mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> > https://www.redhat.com/mailman/listinfo/redhat-list
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
