From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Daniel Wagner <dwagner@suse.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Hannes Reinecke <hare@suse.de>, Sagi Grimberg <sagi@grimberg.me>,
Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH blktests v3 0/3] Introduce nvmet target setup/cleanup helpers
Date: Tue, 22 Aug 2023 17:54:48 +0000 [thread overview]
Message-ID: <f51b5ea8-a9e7-8bb2-983f-b46b44eb3776@nvidia.com> (raw)
In-Reply-To: <20230822083812.24612-1-dwagner@suse.de>
On 8/22/23 01:38, Daniel Wagner wrote:
> Addressed Sagi's feedback and dropped the explicit --blkdev=device argument from
> the _nvmet_target_setup calls, as it is the default.
>
>
>
> original cover letter:
>
> Introduce helpers to setup nvmet targets. This is spin off from the refactoring
> patches and the allowed_host patches [1].
>
> Sagi suggested to record all resources allocated by nvmet_target_setup and then
> later clean them up in nvmet_target_cleanup. I opted to figure out in
> nvmet_target_cleanup what was allocated via the newly introdcuded _get_nvmet_ports
> helper. The reason being, Hannes told me offline that he would like to add ANA
> tests which will add some more ports to the subsystem. I hope with this
> the code is more future proof.
>
> BTW, while looking at this I saw that the passthru code is using the awkward
> return value port when calling nvmet_passthru_target_setup. It seems some
> more refactoring is in order...
>
> [1] https://lore.kernel.org/linux-nvme/5h333eqhtw252sjw6axjewlb5bbb5ze7awekczxe3kie2lnhw6@manyer42khct/
>
>
> changes
>
> v3:
> - rebased/retested
> - use the default with _nvmet_target_setup
>
> v2:
> - drop local subsys variable in passthru tests
> - do not use port as handle in passthru tests
> - free port after unregistering from subsys
> - https://lore.kernel.org/linux-nvme/20230818141537.22332-1-dwagner@suse.de/
>
> v1:
> - https://lore.kernel.org/linux-nvme/20230818095744.24619-1-dwagner@suse.de/
>
> Daniel Wagner (3):
> nvme/{033,034,035,036}: use default subsysnqn variable directly
> nvme/{033,034,035,036,37}: drop port handle between passthru target
> setup and cleanup
> nvme: introduce nvmet_target_{setup/cleanup} common code
>
>
I really appreciate you doing this cleanup, it was long due.
Thanks a lot, for this series :-
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
prev parent reply other threads:[~2023-08-22 17:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 8:38 Daniel Wagner
2023-08-22 8:38 ` [PATCH blktests v3 1/3] nvme/{033,034,035,036}: use default subsysnqn variable directly Daniel Wagner
2023-08-22 8:38 ` [PATCH blktests v3 2/3] nvme/{033,034,035,036,37}: drop port handle between passthru target setup and cleanup Daniel Wagner
2023-08-22 8:38 ` [PATCH blktests v3 3/3] nvme: introduce nvmet_target_{setup/cleanup} common code Daniel Wagner
2023-08-24 3:09 ` Shinichiro Kawasaki
2023-08-24 14:36 ` Bart Van Assche
2023-08-25 0:53 ` Shinichiro Kawasaki
2023-08-25 6:40 ` Daniel Wagner
2023-08-25 7:34 ` Shinichiro Kawasaki
2023-08-25 11:29 ` Daniel Wagner
2023-08-25 13:45 ` Bart Van Assche
2023-08-25 14:26 ` Daniel Wagner
2023-08-25 16:46 ` Bart Van Assche
2023-08-28 4:13 ` Shinichiro Kawasaki
2023-08-28 15:14 ` Bart Van Assche
2023-08-28 17:02 ` Daniel Wagner
2023-08-28 18:55 ` Bart Van Assche
2023-08-29 2:11 ` Shinichiro Kawasaki
2023-08-29 13:35 ` Bart Van Assche
2023-08-30 1:19 ` Shinichiro Kawasaki
2023-09-01 0:33 ` Shinichiro Kawasaki
2023-08-25 6:24 ` Daniel Wagner
2023-08-28 4:17 ` Shinichiro Kawasaki
2023-08-28 15:14 ` Bart Van Assche
2023-08-28 17:03 ` Daniel Wagner
2023-08-22 17:54 ` Chaitanya Kulkarni [this message]
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=f51b5ea8-a9e7-8bb2-983f-b46b44eb3776@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=jgg@ziepe.ca \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.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
all inboxes | Powered by JetHome®