All of lore.kernel.org
 help / color / mirror / Atom feed
From: Todd Gill <tgill@redhat.com>
To: Gris Ge <fge@redhat.com>
Cc: dm-devel@redhat.com
Subject: Re: [PATCH v4 1/1] add display of map information in JSON format
Date: Fri, 20 May 2016 15:59:07 -0400	[thread overview]
Message-ID: <573F6C8B.8080008@redhat.com> (raw)
In-Reply-To: <20160519135032.GA969@redhat.com>


Hi Gris,

On 05/19/2016 09:50 AM, Gris Ge wrote:
> On Wed, May 18, 2016 at 01:26:34PM -0400, Todd Gill wrote:
>>
>> v4:
>>
>> removed space in major_version and minor_version keys.
> Hi Todd,
> 
> Few things:
>     * Please provide path group id from 'pgindex' of struct path.

The paths are contained inside the groups they belong.  Why do we need
the 'pgindex'?

> 
>     * Replace key name 'host adapter' with 'host_adapter'.

I followed what is displayed via 'multipathd show wildcards'.  You are
thinking there should not be spaces in keys?  Valid JSON does allow
spaces in keys.  I thought it was best to be consistent with the
description of the wild card.

>     * Remove output properties as many as you can, only expose
>       those with clear user case and good definition.
>       For API, it's easy to add but hard to remove or change.
>       For example: IMHO, we don't need to expose
>       hcil, next_check, size, serial right now,

These values are already available via the format specifiers for output.
 I think we are already committed to them.

> 
>     * Performance concern. I am getting bad performance(25 seconds
>       while previous 'raw format' way only take 1.5 seconds) on 10k
>       disks. I am still investigating which part slow things down.
> 

There are performance problems with systems that have a large number of
maps (3k+).  But they are not related to the JSON changes.  The JSON
displays in less time than "show maps topology".

I think if we want to address the performance/scale issues - we should
do it with a separate patch set.

Thanks,
Todd

  reply	other threads:[~2016-05-20 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18 17:26 [PATCH v4 0/1] add option to output JSON for multipathd command Todd Gill
2016-05-18 17:26 ` [PATCH v4 1/1] add display of map information in JSON format Todd Gill
2016-05-19 13:50   ` Gris Ge
2016-05-20 19:59     ` Todd Gill [this message]
2016-05-21  1:34       ` Gris Ge

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=573F6C8B.8080008@redhat.com \
    --to=tgill@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=fge@redhat.com \
    /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.