From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Charles Arnold <carnold@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] xentop: Dynamically expand some columns
Date: Mon, 13 Oct 2014 16:09:37 -0400 [thread overview]
Message-ID: <20141013200937.GA3874@laptop.dumpdata.com> (raw)
In-Reply-To: <543BB3A702000091000DD4D7@prv-mh.provo.novell.com>
On Mon, Oct 13, 2014 at 11:12:39AM -0600, Charles Arnold wrote:
> >>> On 10/3/2014 at 03:00 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> > On Thu, 2014-10-02 at 13:05 -0400, Konrad Rzeszutek Wilk wrote:
> >> On Thu, Oct 02, 2014 at 10:25:41AM -0600, Charles Arnold wrote:
> >> > >>> On 10/2/2014 at 10:10 AM, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> >> > > On 02/10/14 16:58, Charles Arnold wrote:
> >> > >> Allow certain xentop columns to automatically expand as the amount
> >> > >> of data reported gets larger. The columns allowed to expand are:
> >> > >>
> >> > >> NETTX(k), NETRX(k), VBD_RD, VBD_WR, VBD_RSECT, VBD_WSECT
> >> > >>
> >> > >> Author: Markus Hauschild <Markus.Hauschild@rz.uni-regensburg.de>
> >> > >> Signed-off-by: Charles Arnold <carnold@suse.com>
> >> > >
> >> > > In principle, very nice. (I have wanted to see about doing this for a
> >> > > while now, but very far down the todo list)
> >> > >
> >> > > How about the NAME field? 9 characters isn't enough for some people.
> >> >
> >> > Sure, and any others that might need it. But what to do about the '-f'
> > flag
> >> > which says show me the full VM name but the flag doesn't adjust the entire
> >> > column. By automatically showing the full name and adjusting the column
> >> > appropriately it makes this flag pointless (which I'm ok with).
> >>
> >> Perhaps this functionality should be under that option?
> >>
> >> I am a bit hesistant about this as there are some users of xentop that
> >> use it for their monitoring. What I can't remember is if they use the
> >> batched mode or not - and if they scan for specific strings (and length).
> >>
> >> This would (I think?) throw a wrench in that?
> >
> > IMHO people who are parsing the output of tools such as this ought to be
> > prepared to deal with occasional changes in the precise content of the
> > output across Xen releases.
> >
> > If they aren't happy with that then they should file wishlist bugs (or
> > better: patches) asking for an extensible/machine-readable format to be
> > output upon request, or for libxenstat to be exposed and made API
> > stable, or some other functionality which solves their need.
> >
> > Otherwise we find ourselves in a position where useful patches like
> > Charles' and similar patches which add genuinely useful output for human
> > readers can never be accepted.
>
> So do we get a thumbs up on this? If so can someone take the patch (I prefer v3 which aligns the name if -f is used, but v2 would satisfy the customer).
I am OK with either patch, so Released-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
on either v2 or v3.
>
> - Charles
>
>
next prev parent reply other threads:[~2014-10-13 20:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 15:58 [PATCH] xentop: Dynamically expand some columns Charles Arnold
2014-10-02 16:10 ` Andrew Cooper
2014-10-02 16:25 ` Charles Arnold
2014-10-02 17:05 ` Konrad Rzeszutek Wilk
2014-10-02 17:27 ` Charles Arnold
2014-10-03 9:00 ` Ian Campbell
2014-10-03 13:34 ` Konrad Rzeszutek Wilk
2014-10-13 17:12 ` Charles Arnold
2014-10-13 20:09 ` Konrad Rzeszutek Wilk [this message]
2014-10-16 13:56 ` Charles Arnold
-- strict thread matches above, loose matches on Subject: below --
2014-10-29 11:24 Markus Hauschild
2014-11-04 10:08 ` Ian Campbell
2014-11-04 17:10 ` Konrad Rzeszutek Wilk
2014-11-05 10:59 ` Ian Campbell
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=20141013200937.GA3874@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=carnold@suse.com \
--cc=xen-devel@lists.xen.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.