public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Alan Adamson <alan.adamson@oracle.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"shinichiro.kawasaki@wdc.com" <shinichiro.kawasaki@wdc.com>
Subject: Re: [PATCH] tests/nvme: Set clear_ids for passthru targets
Date: Wed, 6 Jul 2022 00:18:51 +0000	[thread overview]
Message-ID: <cd910676-cf1d-ae13-94f2-e1ccd59d431d@nvidia.com> (raw)
In-Reply-To: <20220705205632.1720-1-alan.adamson@oracle.com>

On 7/5/22 13:56, Alan Adamson wrote:
> This allows to connect to passthru targets when the client and target
> are on the same host.
> 
> Signed-off-by: Alan Adamson <alan.adamson@oracle.com>
> ---
>   tests/nvme/rc | 3 +++
>   1 file changed, 3 insertions(+)
> 
> diff --git a/tests/nvme/rc b/tests/nvme/rc
> index 4bebbc762cbb..5e50e69fb3f0 100644
> --- a/tests/nvme/rc
> +++ b/tests/nvme/rc
> @@ -303,6 +303,9 @@ _create_nvmet_passthru() {
>   
>   	_test_dev_nvme_ctrl > "${passthru_path}/device_path"
>   	echo 1 > "${passthru_path}/enable"
> +	if [ -f "${passthru_path}/clear_ids" ]; then
> +		echo 1 > "${passthru_path}/clear_ids"
> +	fi
>   }
>   
>   _remove_nvmet_passhtru() {

without looking into the code, just wondering whether we need
an explicit check to ensure that both host and target on the
same machine something like checking nvme_trtype=loop ?

-ck



  reply	other threads:[~2022-07-06  0:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 20:56 [PATCH] tests/nvme: Set clear_ids for passthru targets Alan Adamson
2022-07-06  0:18 ` Chaitanya Kulkarni [this message]
2022-07-06 15:58   ` Alan Adamson
2022-07-14 16:25     ` Alan Adamson
2022-07-15  8:46       ` Shinichiro Kawasaki
2022-07-15 17:22         ` Alan Adamson

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=cd910676-cf1d-ae13-94f2-e1ccd59d431d@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=alan.adamson@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --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