All of lore.kernel.org
 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, 18 Jul 2011 11:10:17 +0200	[thread overview]
Message-ID: <20110718091017.GI3486@nb.net.home> (raw)
In-Reply-To: <20110713034618.GA2968@osiris.boeblingen.de.ibm.com>

On Wed, Jul 13, 2011 at 09:16:18AM +0530, Heiko Carstens wrote:
> thanks. I updated the patch accordingly (see below).

 Applied, thanks.

> Just another thing: there are more per cpu informations that are present
> on s390 that I would also like to the parseable output. However, somehow
> it won't fit to the current approach that lscpu -p prints everything
> with a unique id starting from zero.
> For example the cpus on s390 can be in any of one of the states
> horizontal,vertical:low,vertical:medium or vertical:high (that's just
> an information of how the hypervisor schedules the cpus).
> How is that supposed to be mapped to current approach?
> Map these simply to numbers? E.g. horizontal would be mapped to 0,
> vertical:low would be mapped to 1 and so on?

 Probably, the most important is keep it backwardly compatible ;-)

> Also would I also need a new seperation character between caches and
> new information?

 I'm not sure if the currently used extra separators (,,) for the
 caches is a good idea. Maybe it would be better to force people to
 parse the last comment line where is the header for the columns.

> I'm asking because the output of caches is optional and if something
> new would be added, it seem to get messy in the long term because of
> all seperation characters that may or may not be there. No?

 I agree. Maybe you can add the new things before the caches (as you
 already added 'Book' column).

 The ideal solution is to extend the "-p" functionality and allow to 
 specify expected columns at command line, something like:

    lscpu -p -o cpu,core,book,socket

 We already use the same idea for findmnt and lscpu.

    Karel

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

  reply	other threads:[~2011-07-18  9:10 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
2011-07-13  3:46   ` Heiko Carstens
2011-07-18  9:10     ` Karel Zak [this message]
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=20110718091017.GI3486@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.