Util-Linux package development
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] lscpu: add support for books
Date: Mon, 11 Jul 2011 12:40:35 +0200	[thread overview]
Message-ID: <20110711104035.GH5214@nb.net.home> (raw)
In-Reply-To: <20110705112909.GA3450@osiris.boeblingen.de.ibm.com>

On Tue, Jul 05, 2011 at 01:29:10PM +0200, Heiko Carstens wrote:
> This patch adds support for books in cpu topology output. 

 Thanks!

> Please note that I assume that other programs that get fed by the
> output of lscpu actually parse the last comment line and react in a
> sane way if new entries appear in the cpu list.

 Never assume anything :-)

> Also the readable output is changed from
> "CPU socket(s):" to "Socket(s) per book:" or simply "Socket(s):" in the
> absence of books.

 You're right, the "Socket(s)" is probably better. Unfortunately it's
 not backwardly compatible (for people who use "lscpu | grep ..."), so
 I'll add a note to the ReleaseNotes...

> @@ -732,7 +750,7 @@ print_parsable(struct lscpu_desc *desc)
>  	"# The following is the parsable format, which can be fed to other\n"
>  	"# programs. Each different item in every column has an unique ID\n"
>  	"# starting from zero.\n"
> -	"# CPU,Core,Socket,Node"));
> +	"# CPU,Core,Socket,Book,Node"));

 It would be better to use

    # CPU,Core,Socket,Node,Book

 to keep it usable for stupid scripts where the header is not parsed.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2011-07-11 10:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05 11:29 [PATCH] lscpu: add support for books Heiko Carstens
2011-07-11 10:40 ` Karel Zak [this message]
2011-07-13  3:46   ` Heiko Carstens
2011-07-18  9:10     ` Karel Zak
2011-07-18 15:17       ` Jon Stanley
2011-07-18 22:21         ` Karel Zak
2011-07-27 21:35           ` Karel Zak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110711104035.GH5214@nb.net.home \
    --to=kzak@redhat.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox