Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Nilay Shroff <nilay@linux.ibm.com>, linux-nvme@lists.infradead.org
Cc: dwagner@suse.de, hare@kernel.org, kbusch@kernel.org, gjoyce@ibm.com
Subject: Re: [PATCHv2 4/4] test: extend sysfs tree dump test
Date: Tue, 22 Apr 2025 08:28:48 +0200	[thread overview]
Message-ID: <949760d8-c279-4899-bf4f-62290d78fee6@suse.de> (raw)
In-Reply-To: <20250417135951.239447-5-nilay@linux.ibm.com>

On 4/17/25 15:59, Nilay Shroff wrote:
> In order to validate multipath link support extend the existing sysfs
> tree dump test.
> 
> The updated tree-pcie.tar.xz archive includes a sysfs dump with two
> NVMe subsystems. The nvme-subsys0 simulates a single-port NVMe disk
> with a private namespace that does not support multipath. And another
> nvme-subsys1 simulates a dual-port NVMe disk with a shared namespace
> attached to multiple controllers.
> 
> The json tree dump is also updated to include NVMe namespace path
> information. Since the archive content has changed, the expected
> output file tree-pcie.out is also updated to reflect the new structure.
> 
> Signed-off-by: Nilay Shroff <nilay@linux.ibm.com>
> ---
>   src/nvme/json.c                  |  90 +++++++++++++++++++++++++++----
>   test/sysfs/data/tree-pcie.out    |  53 ++++++++++++++----
>   test/sysfs/data/tree-pcie.tar.xz | Bin 19712 -> 12656 bytes
>   3 files changed, 124 insertions(+), 19 deletions(-)
> 
Not a big fan of having tar.gz files in git. Can't we create it on the
fly and only store text files?

Otherwise:

Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                  Kernel Storage Architect
hare@suse.de                                +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich


  reply	other threads:[~2025-04-22  6:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 13:59 [PATCHv2 0/4] libnvme: add support for discovering multipath of a shared ns Nilay Shroff
2025-04-17 13:59 ` [PATCHv2 1/4] tree: add support for discovering nvme paths using sysfs multipath link Nilay Shroff
2025-04-22  6:24   ` Hannes Reinecke
2025-04-22 14:01     ` Nilay Shroff
2025-04-17 13:59 ` [PATCHv2 2/4] tree: add queue-depth attribute for nvme path object Nilay Shroff
2025-04-22  6:26   ` Hannes Reinecke
2025-04-22 14:32     ` Nilay Shroff
2025-04-22 17:23       ` Daniel Wagner
2025-04-23  6:13         ` Nilay Shroff
2025-04-17 13:59 ` [PATCHv2 3/4] tree: add attribute numa_nodes for NVMe " Nilay Shroff
2025-04-22  6:27   ` Hannes Reinecke
2025-04-17 13:59 ` [PATCHv2 4/4] test: extend sysfs tree dump test Nilay Shroff
2025-04-22  6:28   ` Hannes Reinecke [this message]
2025-04-22 10:09     ` Daniel Wagner

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=949760d8-c279-4899-bf4f-62290d78fee6@suse.de \
    --to=hare@suse.de \
    --cc=dwagner@suse.de \
    --cc=gjoyce@ibm.com \
    --cc=hare@kernel.org \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nilay@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox