From: Ming Lei <ming.lei@redhat.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-doc@vger.kernel.org, linux-block@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, Jonathan Corbet <corbet@lwn.net>,
"Richard W . M . Jones" <rjones@redhat.com>,
ZiyangZhang <ZiyangZhang@linux.alibaba.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Xiaoguang Wang <xiaoguang.wang@linux.alibaba.com>
Subject: Re: [PATCH] Docs: ublk: add ublk document
Date: Tue, 30 Aug 2022 22:13:58 +0800 [thread overview]
Message-ID: <Yw4bJnPdWZPrVJFN@T590> (raw)
In-Reply-To: <21e0e256-c223-5395-d992-040e98ce3308@gmail.com>
On Tue, Aug 30, 2022 at 07:14:51PM +0700, Bagas Sanjaya wrote:
> On 8/28/22 11:50, Ming Lei wrote:
> > +- UBLK_CMD_ADD_DEV
> > + Add one ublk char device(``/dev/ublkc*``) which is talked with ublksrv wrt.
> > + IO command communication. Basic device info is sent together with this
> > + command, see UAPI structure of ublksrv_ctrl_dev_info, such as nr_hw_queues,
> > + queue_depth, and max IO request buffer size, which info is negotiated with
> > + ublk driver and sent back to ublksrv. After this command is completed, the
> > + basic device info can't be changed any more.
> > +
>
> Is "see UAPI structure" means set the structure?
Yes, but some fields may be changed by driver and sent back.
thanks,
Ming
next prev parent reply other threads:[~2022-08-30 14:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 4:50 [PATCH] Docs: ublk: add ublk document Ming Lei
2022-08-28 12:40 ` Bagas Sanjaya
2022-08-28 15:17 ` Randy Dunlap
2022-08-30 8:53 ` Ming Lei
2022-08-28 15:09 ` Richard W.M. Jones
2022-08-29 3:58 ` Gao Xiang
2022-08-30 9:05 ` Ming Lei
2022-08-29 0:18 ` kernel test robot
2022-08-30 12:14 ` Bagas Sanjaya
2022-08-30 14:13 ` Ming Lei [this message]
2022-08-30 15:23 ` Stefan Hajnoczi
2022-08-31 6:31 ` Ziyang Zhang
2022-08-31 20:00 ` Stefan Hajnoczi
2022-09-01 1:34 ` Ming Lei
2022-09-01 2:47 ` Ziyang Zhang
2022-09-01 0:56 ` Ming Lei
2022-09-01 1:04 ` Jens Axboe
2022-09-01 1:35 ` Ming Lei
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=Yw4bJnPdWZPrVJFN@T590 \
--to=ming.lei@redhat.com \
--cc=ZiyangZhang@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=rjones@redhat.com \
--cc=stefanha@redhat.com \
--cc=xiaoguang.wang@linux.alibaba.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 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.