how to get the number of sockets
Broekman, Maarten
Maarten.Broekman at FMR.COM
Wed Aug 19 12:57:43 UTC 2009
If you're using dmidecode and you're lucky, the SMBIOS information will have some type 2 information (for the base board). But that's probably manufacturer dependent. My systems don't have any type 2 data, but the webpage linked below suggests that might have the information you're looking for. You might be able to get it using the serial number and contacting the manufacturer if there's no type 2 data.
Other than that, I'd also be interested in knowing if other people have other ideas (aside from "open the case and look").
Maarten Broekman
> -----Original Message-----
> From: redhat-list-bounces at redhat.com [mailto:redhat-list-
> bounces at redhat.com] On Behalf Of ESGLinux
> Sent: Wednesday, August 19, 2009 5:20 AM
> To: General Red Hat Linux discussion list
> Subject: Re: how to get the number of sockets
>
> Hi All,
> I don´t expect that my question were going to be a great thread but here
> it
> is ;-)
>
> What I have reallized is that is not an easy task.
>
> Perhaps the most accurate answer was to see it on the manufacturer of the
> motherboard specs, so here is the new question, and I hope easier
>
> How Can I get the exact model of the motherboard?
>
> Thank you all for your answers,
>
> ESG
>
>
> 2009/8/18 Broekman, Maarten <Maarten.Broekman at fmr.com>
>
> > DMI type 7 looks like CPU cache information. DMI type 4 is the actual
> > processor information, but from what you've indicated, it doesn't
> report
> > empty sockets.
> >
> > http://linux.die.net/man/8/dmidecode
> >
> > On my machines, I get this as one of the type 7 entries.
> > DMI type 7, 19 bytes.
> > Cache Information
> > Socket Designation: Processor 1 Internal L1 Cache
> > Configuration: Enabled, Not Socketed, Level 1
> > Operational Mode: Write Back
> > Location: Internal
> > Installed Size: 8 KB
> > Maximum Size: 32 KB
> > Supported SRAM Types:
> > Burst
> > Installed SRAM Type: Burst
> > Speed: Unknown
> > Error Correction Type: Unknown
> > System Type: Unknown
> > Associativity: 4-way Set-associative
> >
> > Maarten Broekman
> >
> >
> > > -----Original Message-----
> > > From: redhat-list-bounces at redhat.com [mailto:redhat-list-
> > > bounces at redhat.com] On Behalf Of Marti, Rob
> > > Sent: Tuesday, August 18, 2009 8:53 AM
> > > To: General Red Hat Linux discussion list
> > > Subject: RE: how to get the number of sockets
> > >
> > > 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 at shsu.edu
> > >
> > >
> > > -----Original Message-----
> > > From: redhat-list-bounces at redhat.com [mailto:redhat-list-
> > > bounces at redhat.com] 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 at redhat.com [mailto:redhat-list-
> > > > bounces at redhat.com] 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 at 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 at redhat.com [mailto:redhat-list-
> > > > bounces at redhat.com] 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 at redhat.com [mailto:redhat-list- >
> > > > bounces at redhat.com] 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 at shsu.edu
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: redhat-list-bounces at redhat.com [mailto:redhat-list- >
> > > > bounces at redhat.com] 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 at redhat.com?subject=unsubscribe
> > > > > https://www.redhat.com/mailman/listinfo/redhat-list
> > > > >
> > > > > --
> > > > > redhat-list mailing list
> > > > > unsubscribe
> > > mailto:redhat-list-request at redhat.com?subject=unsubscribe
> > > > > https://www.redhat.com/mailman/listinfo/redhat-list
> > > >
> > > >
> > > > --
> > > > redhat-list mailing list
> > > > unsubscribe
> > mailto:redhat-list-request at redhat.com?subject=unsubscribe
> > > > https://www.redhat.com/mailman/listinfo/redhat-list
> > > >
> > > > --
> > > > redhat-list mailing list
> > > > unsubscribe
> > mailto:redhat-list-request at redhat.com?subject=unsubscribe
> > > > https://www.redhat.com/mailman/listinfo/redhat-list
> > >
> > >
> > > --
> > > redhat-list mailing list
> > > unsubscribe mailto:redhat-list-
> request at redhat.com?subject=unsubscribe
> > > https://www.redhat.com/mailman/listinfo/redhat-list
> > >
> > > --
> > > redhat-list mailing list
> > > unsubscribe mailto:redhat-list-
> request at redhat.com?subject=unsubscribe
> > > https://www.redhat.com/mailman/listinfo/redhat-list
> >
> >
> > --
> > redhat-list mailing list
> > unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> > https://www.redhat.com/mailman/listinfo/redhat-list
> >
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=subscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
More information about the redhat-list
mailing list