From: "Yang, Xiao/杨 晓" <yangx.jy@fujitsu.com>
To: <zwisler@kernel.org>, <toshi.kani@hpe.com>, <jmoyer@redhat.com>
Cc: snitzer@redhat.com, "Shiyang Ruan" <ruansy.fnst@fujitsu.com>,
"y-goto@fujitsu.com" <y-goto@fujitsu.com>,
dm-devel@redhat.com, "Gu, Jinxiang/顾 金香" <gujx@fujitsu.com>,
agk@redhat.com
Subject: [dm-devel] Question about which types of dm need to support DAX
Date: Fri, 16 Sep 2022 14:56:37 +0800 [thread overview]
Message-ID: <e0cce6af-fd55-a582-194e-7f8a3aced6b0@fujitsu.com> (raw)
Hi Ross, Toshi, Jeff and others
After reading the kernel patches[1][2][3] about dm, I think only three
types(linear, stripe and log-writes) of dm can support DAX now, right?
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=98d82f48f1983ceef5c8d2f6c87bfee2918790ee
[2]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=beec25b4573bc310f5a12cf33207b20ecc30945c
[3]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=84b22f8378cf493524043a0a8dd567c58c64546f
In addition, I also saw that Jeff has added a check[4] for the DAX
support of dm in xfstests.
[4]
https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/commit/?id=fc7b3903894a6213c765d64df91847f4460336a2
I wonder why only three types of dm need to support DAX? Is there any
reason/history and use case?
Is it necessary to make other types (for example, thin-pool) support
DAX? If necessary, is there any use case for other types?
Best Regards,
Xiao Yang
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next reply other threads:[~2022-09-16 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 6:56 Yang, Xiao/杨 晓 [this message]
2022-09-20 2:17 ` [dm-devel] Question about which types of dm need to support DAX Yang, Xiao/杨 晓
2022-09-26 19:52 ` Jeff Moyer
2022-09-27 12:42 ` Yang, Xiao/杨 晓
2022-09-27 14:38 ` Jeff Moyer
2022-09-28 7:33 ` y-goto
2022-10-15 8:27 ` Yang, Xiao/杨 晓
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=e0cce6af-fd55-a582-194e-7f8a3aced6b0@fujitsu.com \
--to=yangx.jy@fujitsu.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gujx@fujitsu.com \
--cc=jmoyer@redhat.com \
--cc=ruansy.fnst@fujitsu.com \
--cc=snitzer@redhat.com \
--cc=toshi.kani@hpe.com \
--cc=y-goto@fujitsu.com \
--cc=zwisler@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.