From: John Meneghini <jmeneghi@redhat.com>
To: Martin Belanger <nitram_67@hotmail.com>, linux-nvme@lists.infradead.org
Cc: kbusch@kernel.org, hare@suse.de, axboe@fb.com, hch@lst.de,
sagi@grimberg.me, Martin Belanger <martin.belanger@dell.com>
Subject: Re: [PATCH 3/4] nvme-fabrics: add tp8010 support
Date: Mon, 31 Jan 2022 12:03:03 -0500 [thread overview]
Message-ID: <047b496c-e3a4-bcaa-c542-3f933ed8d54a@redhat.com> (raw)
In-Reply-To: <BL0PR13MB4291A94BED970C6599BBC6679C5F9@BL0PR13MB4291.namprd13.prod.outlook.com>
Hi Martin.
Properly speaking, registrations are sent to the CDC, not the DC.
Correct?
Can we please change this, everywhere, to be clear about when we are "talking" to the CDC (Centralized Discovery Controller) and
when we are talking to the DC (Discovery Controller).
/John
On 1/25/22 09:59, Martin Belanger wrote:
> +/**
> + * nvme_get_adrfam() - Get address family for the address we're registering
> + * with the DC. We retrieve this info from the socket itself. If we can't
> + * get the source address from the socket, then we'll infer the address
> + * family from the address of the DC since the DC address has the same
> + * address family.
> + *
> + * @ctrl: Host NVMe controller instance maintaining the admin queue used to
> + * submit the DIM command to the DC.
> + *
> + * Return: The address family of the source address associated with the
> + * socket connected to the DC.
next prev parent reply other threads:[~2022-01-31 17:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220125145956.14746-1-nitram_67@hotmail.com>
2022-01-25 14:59 ` [PATCH 1/4] nvme-fabrics: add discovery controller type Martin Belanger
2022-01-27 9:16 ` Hannes Reinecke
2022-01-27 13:37 ` Belanger, Martin
2022-01-27 13:16 ` Sagi Grimberg
2022-01-25 14:59 ` [PATCH 2/4] nvme: add host symbolic name Martin Belanger
2022-01-27 9:18 ` Hannes Reinecke
2022-01-27 13:20 ` Sagi Grimberg
2022-01-25 14:59 ` [PATCH 3/4] nvme-fabrics: add tp8010 support Martin Belanger
2022-01-27 9:30 ` Hannes Reinecke
2022-01-27 13:12 ` Sagi Grimberg
2022-01-27 13:30 ` Belanger, Martin
2022-01-27 14:28 ` Hannes Reinecke
2022-01-27 21:59 ` Sagi Grimberg
2022-01-28 17:55 ` Belanger, Martin
2022-01-28 21:49 ` Hannes Reinecke
2022-01-28 23:02 ` Belanger, Martin
2022-01-29 8:43 ` Hannes Reinecke
2022-01-29 12:23 ` Belanger, Martin
2022-01-29 12:47 ` Hannes Reinecke
2022-01-30 8:46 ` Sagi Grimberg
2022-01-30 13:18 ` Sagi Grimberg
2022-01-31 12:08 ` Belanger, Martin
2022-01-31 16:05 ` Sagi Grimberg
2022-01-31 16:16 ` Belanger, Martin
2022-01-31 18:56 ` Sagi Grimberg
2022-02-02 8:36 ` Hannes Reinecke
2022-01-31 17:03 ` John Meneghini [this message]
2022-01-31 17:17 ` Belanger, Martin
2022-01-31 18:28 ` John Meneghini
2022-01-25 14:59 ` [PATCH 4/4] nvme-fabrics: add explicit deregistration on disconnect Martin Belanger
2022-01-27 9:31 ` Hannes Reinecke
2022-01-27 13:14 ` 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=047b496c-e3a4-bcaa-c542-3f933ed8d54a@redhat.com \
--to=jmeneghi@redhat.com \
--cc=axboe@fb.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.belanger@dell.com \
--cc=nitram_67@hotmail.com \
--cc=sagi@grimberg.me \
/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.