From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Dongsheng Yang <dongsheng.yang@easystack.cn>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
Dongsheng Yang <dongsheng.yang.linux@gmail.com>
Subject: Re: [PATCH 1/7] block: Init for CBD(CXL Block Device)
Date: Wed, 24 Apr 2024 03:58:42 +0000 [thread overview]
Message-ID: <c345a609-8114-4dc7-a223-186728cac41f@nvidia.com> (raw)
In-Reply-To: <20240422071606.52637-2-dongsheng.yang@easystack.cn>
> +/*
> + * As shared memory is supported in CXL3.0 spec, we can transfer data via CXL shared memory.
> + * CBD means CXL block device, it use CXL shared memory to transport command and data to
> + * access block device in different host, as shown below:
> + *
> + * ┌───────────────────────────────┐ ┌────────────────────────────────────┐
> + * │ node-1 │ │ node-2 │
> + * ├───────────────────────────────┤ ├────────────────────────────────────┤
> + * │ │ │ │
> + * │ ┌───────┤ ├─────────┐ │
> + * │ │ cbd0 │ │ backend0├──────────────────┐ │
> + * │ ├───────┤ ├─────────┤ │ │
> + * │ │ pmem0 │ │ pmem0 │ ▼ │
> + * │ ┌───────┴───────┤ ├─────────┴────┐ ┌───────────────┤
> + * │ │ cxl driver │ │ cxl driver │ │ /dev/sda │
> + * └───────────────┴────────┬──────┘ └─────┬────────┴─────┴───────────────┘
> + * │ │
> + * │ │
> + * │ CXL CXL │
> + * └────────────────┐ ┌───────────┘
> + * │ │
> + * │ │
> + * │ │
> + * ┌───┴───────────────┴─────┐
> + * │ shared memory device │
> + * └─────────────────────────┘
> + *
> + * any read/write to cbd0 on node-1 will be transferred to node-2 /dev/sda. It works similar with
> + * nbd (network block device), but it transfer data via CXL shared memory rather than network.
> + */
> +
> +/* printk */
I don't think you need above comment ..
> +#define cbd_err(fmt, ...) \
> + pr_err("cbd: %s:%u " fmt, __func__, __LINE__, ##__VA_ARGS__)
you can use #define pr_fmt and remove cmd: prefixes in each pr_xxx above ?
> +#define cbd_info(fmt, ...) \
> + pr_info("cbd: %s:%u " fmt, __func__, __LINE__, ##__VA_ARGS__)
> +#define cbd_debug(fmt, ...) \
> + pr_debug("cbd: %s:%u " fmt, __func__, __LINE__, ##__VA_ARGS__)
> +
> +#define cbdt_err(transport, fmt, ...) \
> + cbd_err("cbd_transport%u: " fmt, \
> + transport->id, ##__VA_ARGS__)
> +#define cbdt_info(transport, fmt, ...) \
> + cbd_info("cbd_transport%u: " fmt, \
> + transport->id, ##__VA_ARGS__)
> +#define cbdt_debug(transport, fmt, ...) \
> + cbd_debug("cbd_transport%u: " fmt, \
> + transport->id, ##__VA_ARGS__)
> +
> +#define cbd_backend_err(backend, fmt, ...) \
> + cbdt_err(backend->cbdt, "backend%d: " fmt, \
> + backend->backend_id, ##__VA_ARGS__)
> +#define cbd_backend_info(backend, fmt, ...) \
> + cbdt_info(backend->cbdt, "backend%d: " fmt, \
> + backend->backend_id, ##__VA_ARGS__)
> +#define cbd_backend_debug(backend, fmt, ...) \
> + cbdt_debug(backend->cbdt, "backend%d: " fmt, \
> + backend->backend_id, ##__VA_ARGS__)
> +
> +#define cbd_handler_err(handler, fmt, ...) \
> + cbd_backend_err(handler->cbdb, "handler%d: " fmt, \
> + handler->channel.channel_id, ##__VA_ARGS__)
> +#define cbd_handler_info(handler, fmt, ...) \
> + cbd_backend_info(handler->cbdb, "handler%d: " fmt, \
> + handler->channel.channel_id, ##__VA_ARGS__)
> +#define cbd_handler_debug(handler, fmt, ...) \
> + cbd_backend_debug(handler->cbdb, "handler%d: " fmt, \
> + handler->channel.channel_id, ##__VA_ARGS__)
> +
> +#define cbd_blk_err(dev, fmt, ...) \
> + cbdt_err(dev->cbdt, "cbd%d: " fmt, \
> + dev->mapped_id, ##__VA_ARGS__)
> +#define cbd_blk_info(dev, fmt, ...) \
> + cbdt_info(dev->cbdt, "cbd%d: " fmt, \
> + dev->mapped_id, ##__VA_ARGS__)
> +#define cbd_blk_debug(dev, fmt, ...) \
> + cbdt_debug(dev->cbdt, "cbd%d: " fmt, \
> + dev->mapped_id, ##__VA_ARGS__)
> +
> +#define cbd_queue_err(queue, fmt, ...) \
> + cbd_blk_err(queue->cbd_blkdev, "queue-%d: " fmt, \
> + queue->index, ##__VA_ARGS__)
> +#define cbd_queue_info(queue, fmt, ...) \
> + cbd_blk_info(queue->cbd_blkdev, "queue-%d: " fmt, \
> + queue->index, ##__VA_ARGS__)
> +#define cbd_queue_debug(queue, fmt, ...) \
> + cbd_blk_debug(queue->cbd_blkdev, "queue-%d: " fmt, \
> + queue->index, ##__VA_ARGS__)
> +
> +#define cbd_channel_err(channel, fmt, ...) \
> + cbdt_err(channel->cbdt, "channel%d: " fmt, \
> + channel->channel_id, ##__VA_ARGS__)
> +#define cbd_channel_info(channel, fmt, ...) \
> + cbdt_info(channel->cbdt, "channel%d: " fmt, \
> + channel->channel_id, ##__VA_ARGS__)
> +#define cbd_channel_debug(channel, fmt, ...) \
> + cbdt_debug(channel->cbdt, "channel%d: " fmt, \
> + channel->channel_id, ##__VA_ARGS__)
> +
[...]
> +
> +struct cbd_se {
> + struct cbd_se_hdr header;
> + u64 priv_data; // pointer to cbd_request
use /**/ instead //
-ck
next prev parent reply other threads:[~2024-04-24 3:58 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 7:15 [PATCH RFC 0/7] block: Introduce CBD (CXL Block Device) Dongsheng Yang
2024-04-22 7:16 ` [PATCH 1/7] block: Init for CBD(CXL " Dongsheng Yang
2024-04-22 18:39 ` Randy Dunlap
2024-04-22 22:41 ` Dongsheng Yang
2024-04-24 3:58 ` Chaitanya Kulkarni [this message]
2024-04-24 8:36 ` Dongsheng Yang
2024-04-22 7:16 ` [PATCH 2/7] cbd: introduce cbd_transport Dongsheng Yang
2024-04-24 4:08 ` Chaitanya Kulkarni
2024-04-24 8:43 ` Dongsheng Yang
2024-04-22 7:16 ` [PATCH 3/7] cbd: introduce cbd_channel Dongsheng Yang
2024-04-22 7:16 ` [PATCH 4/7] cbd: introduce cbd_host Dongsheng Yang
2024-04-25 5:51 ` [EXTERNAL] " Bharat Bhushan
2024-04-22 7:16 ` [PATCH 5/7] cbd: introuce cbd_backend Dongsheng Yang
2024-04-24 5:03 ` Chaitanya Kulkarni
2024-04-24 8:36 ` Dongsheng Yang
2024-04-25 5:46 ` [EXTERNAL] " Bharat Bhushan
2024-04-22 7:16 ` [PATCH 7/7] cbd: add related sysfs files in transport register Dongsheng Yang
2024-04-25 5:24 ` [EXTERNAL] " Bharat Bhushan
2024-04-22 22:42 ` [PATCH 6/7] cbd: introduce cbd_blkdev Dongsheng Yang
2024-04-23 7:27 ` Dongsheng Yang
2024-04-24 4:29 ` [PATCH RFC 0/7] block: Introduce CBD (CXL Block Device) Dan Williams
2024-04-24 6:33 ` Dongsheng Yang
2024-04-24 15:14 ` Gregory Price
2024-04-26 1:25 ` Dongsheng Yang
2024-04-26 13:48 ` Gregory Price
2024-04-26 14:53 ` Dongsheng Yang
2024-04-26 16:14 ` Gregory Price
2024-04-28 5:47 ` Dongsheng Yang
2024-04-28 16:44 ` Gregory Price
2024-04-28 16:55 ` John Groves
2024-05-03 9:52 ` Jonathan Cameron
2024-05-08 11:39 ` Dongsheng Yang
2024-05-08 12:11 ` Jonathan Cameron
2024-05-08 13:03 ` Dongsheng Yang
2024-05-08 15:44 ` Jonathan Cameron
2024-05-09 11:24 ` Dongsheng Yang
2024-05-09 12:21 ` Jonathan Cameron
2024-05-09 13:03 ` Dongsheng Yang
2024-05-21 18:41 ` Dan Williams
2024-05-22 6:17 ` Dongsheng Yang
2024-05-29 15:25 ` Gregory Price
2024-05-30 6:59 ` Dongsheng Yang
2024-05-30 13:38 ` Jonathan Cameron
2024-06-01 3:22 ` Dan Williams
2024-06-03 12:48 ` Jonathan Cameron
2024-06-03 17:28 ` James Morse
2024-06-04 14:26 ` Jonathan Cameron
2024-05-31 14:23 ` Gregory Price
2024-06-03 1:33 ` Dongsheng Yang
2024-04-30 0:34 ` Dan Williams
2024-04-24 18:08 ` Dan Williams
[not found] ` <539c1323-68f9-d753-a102-692b69049c20@easystack.cn>
2024-04-30 0:10 ` Dan Williams
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=c345a609-8114-4dc7-a223-186728cac41f@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=dan.j.williams@intel.com \
--cc=dongsheng.yang.linux@gmail.com \
--cc=dongsheng.yang@easystack.cn \
--cc=linux-block@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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