From: Leon Romanovsky <leonro@mellanox.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
linux-rdma@vger.kernel.org,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Subject: Re: [PATCH 1/3] ib_srp: Add more documentation
Date: Tue, 15 Feb 2022 20:42:42 +0200 [thread overview]
Message-ID: <Ygv0IhNMJxFHSi8Q@unreal> (raw)
In-Reply-To: <20220215182650.19839-2-bvanassche@acm.org>
On Tue, Feb 15, 2022 at 10:26:48AM -0800, Bart Van Assche wrote:
> Make it more clear what the different ib_srp data structures represent.
>
> Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
> drivers/infiniband/ulp/srp/ib_srp.h | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/ulp/srp/ib_srp.h b/drivers/infiniband/ulp/srp/ib_srp.h
> index abccddeea1e3..55a575e2cace 100644
> --- a/drivers/infiniband/ulp/srp/ib_srp.h
> +++ b/drivers/infiniband/ulp/srp/ib_srp.h
> @@ -92,6 +92,9 @@ enum srp_iu_type {
> };
>
> /*
> + * RDMA adapter in the initiator system.
> + *
> + * @dev_list: List of RDMA ports associated with this RDMA adapter (srp_host).
Isn't this list of RDMA devices and not ports?
> * @mr_page_mask: HCA memory registration page mask.
> * @mr_page_size: HCA memory registration page size.
> * @mr_max_size: Maximum size in bytes of a single FR registration request.
> @@ -109,6 +112,12 @@ struct srp_device {
> bool use_fast_reg;
> };
>
> +/*
> + * One port of an RDMA adapter in the initiator system.
> + *
> + * @target_list: List of connected target ports (struct srp_target_port).
> + * @target_lock: Protects @target_list.
> + */
> struct srp_host {
> struct srp_device *srp_dev;
> u8 port;
> @@ -183,7 +192,7 @@ struct srp_rdma_ch {
> };
>
> /**
> - * struct srp_target_port
> + * struct srp_target_port - RDMA port in the SRP target system
> * @comp_vector: Completion vector used by the first RDMA channel created for
> * this target port.
> */
next prev parent reply other threads:[~2022-02-15 18:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 18:26 [PATCH 0/3] Fix a deadlock in the ib_srp driver Bart Van Assche
2022-02-15 18:26 ` [PATCH 1/3] ib_srp: Add more documentation Bart Van Assche
2022-02-15 18:42 ` Leon Romanovsky [this message]
2022-02-15 20:34 ` Bart Van Assche
2022-02-16 7:02 ` Leon Romanovsky
2022-02-15 18:26 ` [PATCH 2/3] ib_srp: Protect the target list with a mutex instead of a spinlock Bart Van Assche
2022-02-15 18:44 ` Leon Romanovsky
2022-02-15 20:35 ` Bart Van Assche
2022-02-15 18:26 ` [PATCH 3/3] ib_srp: Fix a deadlock Bart Van Assche
2022-02-15 18:51 ` Leon Romanovsky
2022-02-15 20:37 ` Bart Van Assche
2022-02-15 20:41 ` Jason Gunthorpe
2022-02-15 20:50 ` Bart Van Assche
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=Ygv0IhNMJxFHSi8Q@unreal \
--to=leonro@mellanox.com \
--cc=bvanassche@acm.org \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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