All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gris Ge <fge@redhat.com>
To: Todd Gill <tgill@redhat.com>
Cc: dm-devel@redhat.com
Subject: Re: [PATCH v4 1/1] add display of map information in JSON format
Date: Thu, 19 May 2016 21:50:32 +0800	[thread overview]
Message-ID: <20160519135032.GA969@redhat.com> (raw)
In-Reply-To: <1463592394-18974-2-git-send-email-tgill@redhat.com>


[-- Attachment #1.1: Type: text/plain, Size: 822 bytes --]

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.

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

    * 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,

    * 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.

Thank you.
Best regards.

-- 
Gris Ge

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2016-05-19 13:50 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 [this message]
2016-05-20 19:59     ` Todd Gill
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=20160519135032.GA969@redhat.com \
    --to=fge@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=tgill@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.