From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH v2 07/10] nvme-cli: Add routine to search for controller with specific attributes
Date: Sat, 20 Jul 2019 17:25:04 +0900 [thread overview]
Message-ID: <20190720082504.GG22395@minwoo-desktop> (raw)
In-Reply-To: <20190719225305.11397-8-jsmart2021@gmail.com>
On 19-07-19 15:53:02, James Smart wrote:
> In preparation for searching controllers to match with connect args:
>
> Create a new routine find_ctrl_with_connectargs() that will search the
> controllers that exist in the system to find one that has attributes
> that match the connect arguments specified. If found, the routine
> returns the controller name ("nvme?"). If not found, a NULL is returned.
>
> Routine is defined as a global as a subsequent patch will use it
> from the fabrics routines.
>
> Signed-off-by: James Smart <jsmart2021 at gmail.com>
> Reviewed-by: Sagi Grimberg <sagi at grimberg.me>
> Reviewed-by: Hannes Reinecke <hare at suse.com>
>
> ---
> v2:
> change "ctlr" to "ctrl" in fprintf
This looks good to me.
Reviewed-by: Minwoo Im <minwoo.im.dev at gmail.com>
> ---
> nvme.c | 37 +++++++++++++++++++++++++++++++++++++
> nvme.h | 1 +
> 2 files changed, 38 insertions(+)
>
> diff --git a/nvme.c b/nvme.c
> index 7f706c8..e4fdb4e 100644
> --- a/nvme.c
> +++ b/nvme.c
> @@ -2048,6 +2048,43 @@ cleanup_exit:
> return found;
> }
>
> +/*
> + * Look through the system to find an existing controller whose
> + * attributes match the connect arguments specified
> + * If found, a string containing the controller name (ex: "nvme?")
> + * is returned.
> + * If not found, a NULL is returned.
> + */
> +char *find_ctrl_with_connectargs(struct connect_args *args)
> +{
> + struct dirent **devices;
> + char *devname = NULL;
> + int i, n;
> +
> + n = scandir(SYS_NVME, &devices, scan_ctrls_filter, alphasort);
> + if (n < 0) {
> + fprintf(stderr, "no NVMe controller(s) detected.\n");
> + return NULL;
> + }
> +
> + for (i = 0; i < n; i++) {
> + if (ctrl_matches_connectargs(devices[i]->d_name, args)) {
James,
It might be too late to discuss about this argument, but did you decided
to have (struct connect_args) as a parameter for this function?
Sorry for not giving any thoughts on the following mail[1], but I would
prefer not introducing a new data structure for this because it's just a
bypass argument from a perspective of find_ctrl_with_connetargs(). But
If you think it's okay to go with, then I'm fine with that too.
[1] http://lists.infradead.org/pipermail/linux-nvme/2019-July/025646.html
Thanks!
next prev parent reply other threads:[~2019-07-20 8:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 22:52 [PATCH v2 00/10] nvme-cli: nvmf auto-connect scripts James Smart
2019-07-19 22:52 ` [PATCH v2 01/10] nvme-cli: ignore arguments that pass in "none" James Smart
2019-07-19 22:52 ` [PATCH v2 02/10] nvme-cli: support persistent connections to a discovery controller James Smart
2019-07-19 22:52 ` [PATCH v2 03/10] nvme-cli: allow discover to address discovery controller by persistent name James Smart
2019-07-19 22:52 ` [PATCH v2 04/10] nvme-cli: Refactor to create a get_nvme_ctrl_info routine James Smart
2019-07-19 22:53 ` [PATCH v2 05/10] nvme-cli: extend ctrl_list_item for connect attributes James Smart
2019-07-19 22:53 ` [PATCH v2 06/10] nvme-cli: Add routine to compare ctrl_list_item to connect args James Smart
2019-07-19 22:53 ` [PATCH v2 07/10] nvme-cli: Add routine to search for controller with specific attributes James Smart
2019-07-20 8:25 ` Minwoo Im [this message]
2019-07-20 18:33 ` James Smart
2019-07-22 22:41 ` Sagi Grimberg
2019-07-23 13:36 ` Minwoo Im
2019-07-19 22:53 ` [PATCH v2 08/10] nvme-cli: Expand --device argument processing James Smart
2019-07-19 22:53 ` [PATCH v2 09/10] nvme-cli: add --quiet option James Smart
2019-07-19 22:53 ` [PATCH v2 10/10] nvme-cli: nvmf auto-connect scripts James Smart
2019-07-23 2:52 ` Sagi Grimberg
2019-07-23 16:01 ` James Smart
2019-07-23 3:57 ` Sagi Grimberg
2019-07-23 16:04 ` James Smart
2019-07-23 17:32 ` Sagi Grimberg
2019-07-24 16:38 ` James Smart
2019-07-24 18:15 ` Sagi Grimberg
2019-07-24 23:45 ` James Smart
2019-07-22 22:43 ` [PATCH v2 00/10] " Sagi Grimberg
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=20190720082504.GG22395@minwoo-desktop \
--to=minwoo.im.dev@gmail.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