From: Dongsheng Yang <dongsheng.yang@linux.dev>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: mpatocka@redhat.com, agk@redhat.com, snitzer@kernel.org,
axboe@kernel.dk, hch@lst.de, dan.j.williams@intel.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev,
dm-devel@lists.linux.dev
Subject: Re: [PATCH v1 02/11] dm-pcache: add backing device management
Date: Mon, 7 Jul 2025 14:25:06 +0800 [thread overview]
Message-ID: <e9386b67-9c4c-415e-91d8-511ac8d0ded5@linux.dev> (raw)
In-Reply-To: <20250701145650.00004e72@huawei.com>
在 7/1/2025 9:56 PM, Jonathan Cameron 写道:
> On Tue, 24 Jun 2025 07:33:49 +0000
> Dongsheng Yang <dongsheng.yang@linux.dev> wrote:
>
>> This patch introduces *backing_dev.{c,h}*, a self-contained layer that
>> handles all interaction with the *backing block device* where cache
>> write-back and cache-miss reads are serviced. Isolating this logic
>> keeps the core dm-pcache code free of low-level bio plumbing.
>>
>> * Device setup / teardown
>> - Opens the target with `dm_get_device()`, stores `bdev`, file and
>> size, and initialises a dedicated `bioset`.
>> - Gracefully releases resources via `backing_dev_stop()`.
>>
>> * Request object (`struct pcache_backing_dev_req`)
>> - Two request flavours:
>> - REQ-type – cloned from an upper `struct bio` issued to
>> dm-pcache; trimmed and re-targeted to the backing LBA.
>> - KMEM-type – maps an arbitrary kernel memory buffer
>> into a freshly built.
>> - Private completion callback (`end_req`) propagates status to the
>> upper layer and handles resource recycling.
>>
>> * Submission & completion path
>> - Lock-protected submit queue + worker (`req_submit_work`) let pcache
>> push many requests asynchronously, at the same time, allow caller
>> to submit backing_dev_req in atomic context.
>> - End-io handler moves finished requests to a completion list processed
>> by `req_complete_work`, ensuring callbacks run in process context.
>> - Direct-submit option for non-atomic context.
>>
>> * Flush
>> - `backing_dev_flush()` issues a flush to persist backing-device data.
>>
>> Signed-off-by: Dongsheng Yang <dongsheng.yang@linux.dev>
>> ---
>> drivers/md/dm-pcache/backing_dev.c | 292 +++++++++++++++++++++++++++++
>> drivers/md/dm-pcache/backing_dev.h | 88 +++++++++
>> 2 files changed, 380 insertions(+)
>> create mode 100644 drivers/md/dm-pcache/backing_dev.c
>> create mode 100644 drivers/md/dm-pcache/backing_dev.h
>> +
>> +struct pcache_backing_dev_req *backing_dev_req_create(struct pcache_backing_dev *backing_dev,
>> + struct pcache_backing_dev_req_opts *opts)
>> +{
>> + if (opts->type == BACKING_DEV_REQ_TYPE_REQ)
>> + return req_type_req_create(backing_dev, opts);
>> + else if (opts->type == BACKING_DEV_REQ_TYPE_KMEM)
>>
> returned in earlier branch so go with simpler
>
> if (opts->type..)
Hi Jonathan,
This looks good, I am willing to do this change.
Thanx
Dongsheng
> Or use a switch statement if you expect to get more entries in this over time.
>
>> + return kmem_type_req_create(backing_dev, opts);
>> +
>> + return NULL;
>> +}
>> +
>> +void backing_dev_flush(struct pcache_backing_dev *backing_dev)
>> +{
>> + blkdev_issue_flush(backing_dev->dm_dev->bdev);
>> +}
>
next prev parent reply other threads:[~2025-07-07 6:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 7:33 [PATCH v1 00/11] dm-pcache – persistent-memory cache for block devices Dongsheng Yang
2025-06-24 7:33 ` [PATCH v1 01/11] dm-pcache: add pcache_internal.h Dongsheng Yang
2025-07-01 13:43 ` Jonathan Cameron
2025-06-24 7:33 ` [PATCH v1 02/11] dm-pcache: add backing device management Dongsheng Yang
2025-07-01 13:56 ` Jonathan Cameron
2025-07-07 6:25 ` Dongsheng Yang [this message]
2025-06-24 7:33 ` [PATCH v1 03/11] dm-pcache: add cache device Dongsheng Yang
2025-07-01 14:07 ` Jonathan Cameron
2025-06-24 7:33 ` [PATCH v1 04/11] dm-pcache: add segment layer Dongsheng Yang
2025-07-01 14:46 ` Jonathan Cameron
2025-07-07 6:24 ` Dongsheng Yang
2025-06-24 7:33 ` [PATCH v1 05/11] dm-pcache: add cache_segment Dongsheng Yang
2025-07-01 14:59 ` Jonathan Cameron
2025-07-07 6:24 ` Dongsheng Yang
2025-06-24 7:33 ` [PATCH v1 06/11] dm-pcache: add cache_writeback Dongsheng Yang
2025-06-24 7:33 ` [PATCH v1 07/11] dm-pcache: add cache_gc Dongsheng Yang
2025-06-24 7:33 ` [PATCH v1 08/11] dm-pcache: add cache_key Dongsheng Yang
2025-06-24 7:33 ` [PATCH v1 09/11] dm-pcache: add cache_req Dongsheng Yang
2025-06-24 7:33 ` [PATCH v1 10/11] dm-pcache: add cache core Dongsheng Yang
2025-06-24 7:33 ` [PATCH v1 11/11] dm-pcache: initial dm-pcache target Dongsheng Yang
2025-06-30 13:30 ` [PATCH v1 00/11] dm-pcache – persistent-memory cache for block devices Mikulas Patocka
2025-06-30 13:40 ` Dongsheng Yang
2025-06-30 14:16 ` Dongsheng Yang
2025-06-30 15:45 ` Mikulas Patocka
2025-06-30 16:30 ` Dongsheng Yang
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=e9386b67-9c4c-415e-91d8-511ac8d0ded5@linux.dev \
--to=dongsheng.yang@linux.dev \
--cc=Jonathan.Cameron@huawei.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=nvdimm@lists.linux.dev \
--cc=snitzer@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 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.