mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jack Wang <jinpu.wang@cloud.ionos.com>,
	linux-block@vger.kernel.org, linux-rdma@vger.kernel.org
Cc: axboe@kernel.dk, hch@infradead.org, sagi@grimberg.me,
	leon@kernel.org, dledford@redhat.com, jgg@ziepe.ca,
	danil.kipnis@cloud.ionos.com, rpenyaev@suse.de,
	pankaj.gupta@cloud.ionos.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 25/26] block/rnbd: a bit of documentation
Date: Sat, 28 Mar 2020 12:40:08 -0700	[thread overview]
Message-ID: <619d2dda-3c4e-a909-ab78-1201057b542c@acm.org> (raw)
In-Reply-To: <20200320121657.1165-26-jinpu.wang@cloud.ionos.com>

On 2020-03-20 05:16, Jack Wang wrote:
> +RNBD (RDMA Network Block Device) is a pair of kernel modules
> +(client and server) that allow for remote access of a block device on
> +the server over RTRS protocol using the RDMA (InfiniBand, RoCE, iWarp)
                                                                   ^^^^^
Isn't this protocol usually spelled as iWARP? See also
https://en.wikipedia.org/wiki/IWARP.

> +dev_search_path option can also contain %SESSNAME% in order to provide
> +different deviec namespaces for different sessions.  See "device_path"
             ^^^^^^
             device?
> +option for details.

Otherwise this patch looks fine to me. Hence:

Reviewed-by: Bart Van Assche <bvanassche@acm.org>

  reply	other threads:[~2020-03-28 19:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200320121657.1165-1-jinpu.wang@cloud.ionos.com>
2020-03-20 12:16 ` [PATCH v11 01/26] sysfs: export sysfs_remove_file_self() Jack Wang
2020-03-20 12:16 ` [PATCH v11 14/26] RDMA/rtrs: a bit of documentation Jack Wang
2020-03-20 12:16 ` [PATCH v11 25/26] block/rnbd: " Jack Wang
2020-03-28 19:40   ` Bart Van Assche [this message]
2020-03-30 10:17     ` Danil Kipnis

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=619d2dda-3c4e-a909-ab78-1201057b542c@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=danil.kipnis@cloud.ionos.com \
    --cc=dledford@redhat.com \
    --cc=hch@infradead.org \
    --cc=jgg@ziepe.ca \
    --cc=jinpu.wang@cloud.ionos.com \
    --cc=leon@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=pankaj.gupta@cloud.ionos.com \
    --cc=rpenyaev@suse.de \
    --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 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®