{"id":2950,"date":"2018-03-01T13:04:36","date_gmt":"2018-03-01T10:04:36","guid":{"rendered":"https:\/\/www.howtoforge.com\/linux-lscpu-command\/"},"modified":"2018-03-01T13:04:36","modified_gmt":"2018-03-01T10:04:36","slug":"linux-lscpu-command-tutorial-for-beginners-5-examples","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/linux-lscpu-command-tutorial-for-beginners-5-examples\/","title":{"rendered":"Linux lscpu Command Tutorial for Beginners (5 Examples)"},"content":{"rendered":"

We’ve already discussed the lshw command, which fetches data related to your system’s hardware. However, if you are only interested in CPU-related information, there’s a dedicated command line utility for that was well: lscpu<\/strong>. In this article, we will discuss this tool using some easy to understand examples.<\/p>\n

But before we do that, it’s worth mentioning that all examples in this tutorial have been tested on Ubuntu 16.04 LTS.<\/p>\n

Linux lscpu command<\/h2>\n

The lscpu command in Linux displays information about the CPU architecture.\u00a0 Here’s the syntax of the tool:<\/p>\n

lscpu [-a|-b|-c] [-x] [-s directory] [-e[=list]|-p[=list]]lscpu -h|-V<\/p>\n

And here’s what the man page says about it:<\/p>\n

 lscpu\u00a0 gathers\u00a0 CPU\u00a0 architecture\u00a0 information from sysfs and \/proc\/cpuinfo.\u00a0 The command output can be optimized for parsing or for easy readability by humans.\u00a0 The information includes, for example, the number of CPUs, threads,\u00a0 cores,\u00a0 sockets,\u00a0 and\u00a0 Non-Uniform\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Memory\u00a0 Access (NUMA) nodes. There is also information about the CPU caches and cache sharing, family, model, bogoMIPS, byte order, and stepping.
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Options that result in an output table have a list argument. Use this argument to customize the command output. Specify a comma separated list of column labels to limit the output table to only the specified columns, arranged in the specified order. See COLUMNS for a list of valid column labels. The column labels are not case sensitive.<\/p>
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Not all columns are supported on all architectures. If an unsupported column is specified, lscpu prints the column but does not provide any data for it.<\/p><\/pre>\n
The following Q&A-styled examples should give you a better idea on how this tool works.<\/p>\n
Q1. How to use lscpu command?<\/h2>\n
Basic usage is pretty straight forward – all you have to do is to run the ‘lscpu’ command sans any options.<\/p>\n
lscpu<\/p>\n
\"How<\/a><\/p>\n
Q2. How to make lscpu display information in human readable format?<\/h2>\n
There exists a specific command line option -e<\/strong> that lets you do this.<\/p>\n
lscpu -e<\/p>\n
For example, here’s what the aforementioned command produced in output:<\/p>\n
\"How<\/a><\/p>\n
If you want, you can also limit the output to specific columns. For example, the following command limits the output to CPU and NODE columns.<\/p>\n
lscpu -e=cpu,node<\/p>\n
\"lscpu<\/a><\/p>\n
Q3. How to limit the output to only online or offline CPUs?<\/h2>\n
The lscpu command lets you limit the output it produces to only online or offline CPUs. You can do this using the -b<\/strong> and -c<\/strong> command line options, respectively.<\/p>\n
lscpu -b<\/p>\n
lscpu -c<\/p>\n
Note that both these command line options may only be specified together with option -e<\/strong> or -p<\/strong>.<\/p>\n
Q4. How to make lscpu display output in parsing-friendly format?<\/h2>\n
You can do this using the -p<\/strong> command line option.<\/p>\n
lscpu -p<\/p>\n
Following is the output this command produced in my case:<\/p>\n
\"How<\/a><\/p>\n
Note that just like in the case of -e<\/strong> option, you can also limit the output in this case by passing the ‘list’ argument.<\/p>\n
–parse[=list]\n
Here’s what the man page has to say about the ‘list’ argument:<\/p>\n
If the list argument is omitted, the command output is compatible with earlier versions of lscpu. In this compatible format, two commas are used to separate CPU cache columns. If no CPU caches are identified the cache column is omitted.
If the list argument is used, cache columns are separated with a colon (:). When specifying the list argument, the string of option, equal sign (=), and list must not contain any blanks or other whitespace. Examples: '-p=cpu,node' or '--parse=cpu,node'.<\/p><\/pre>\n
Q5. How to make lscpu use hexadecimal masks for CPU sets?<\/h2>\n
By default, lscpu prints CPU sets in list format (for example 0,1). However, if you want, you can have lscpu use\u00a0hexadecimal masks for CPU sets, something which you can do using the -x<\/strong> command line option.<\/p>\n
lscpu -x<\/p>\n
\"How<\/a><\/p>\n
Conclusion<\/h2>\n
Like lshw, the lscpu command is also not something that you’ll require everyday, but it may save your day when the requirement arises. Here, in this tutorial, we have discussed majority of features (command line options) it offers, so practice these, and when done, head to the tool’s\u00a0man page<\/a> to know more.<\/p>\n
\n
Share this page:<\/b><\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"
We’ve already discussed the lshw command, which fetches data related to your system’s hardware. However, if you are only interested in CPU-related information, there’s a dedicated command line utility for that was well: lscpu. In this article, we will discuss this tool using some easy to understand examples. But before we do that, it’s worth …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[],"class_list":["post-2950","post","type-post","status-publish","format-standard","hentry","category-36"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/2950","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=2950"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/2950\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=2950"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=2950"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=2950"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}