From: Guoqing Jiang <guoqing.jiang@linux.dev>
To: "Daisuke Matsuda (Fujitsu)" <matsuda-daisuke@fujitsu.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"leonro@nvidia.com" <leonro@nvidia.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"zyjzyj2000@gmail.com" <zyjzyj2000@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rpearsonhpe@gmail.com" <rpearsonhpe@gmail.com>,
"Xiao Yang (Fujitsu)" <yangx.jy@fujitsu.com>,
"Zhijian Li (Fujitsu)" <lizhijian@fujitsu.com>,
"Yasunori Gotou (Fujitsu)" <y-goto@fujitsu.com>
Subject: Re: [PATCH for-next v5 0/7] On-Demand Paging on SoftRoCE
Date: Fri, 19 May 2023 18:20:47 +0800 [thread overview]
Message-ID: <e13270a2-c149-6194-b283-06fc38efbd9b@linux.dev> (raw)
In-Reply-To: <TYCPR01MB8455648A5C9DFFB37FFB172FE57C9@TYCPR01MB8455.jpnprd01.prod.outlook.com>
On 5/19/23 17:57, Daisuke Matsuda (Fujitsu) wrote:
> On Fri, May 19, 2023 3:42 PM Guoqing Jiang wrote:
>> Hello,
>>
>> On 5/18/23 16:21, Daisuke Matsuda wrote:
>>> [2] [PATCH for-next v3 0/7] On-Demand Paging on SoftRoCE
>>> https://lore.kernel.org/lkml/cover.1671772917.git.matsuda-daisuke@fujitsu.com/
>> Quote from above link
>>
>> "There is a problem that data on DAX-enabled filesystem cannot be
>> duplicated with
>> software RAID or other hardware methods."
>>
>> Could you elaborate a bit more about the problem or any links about it?
>> Thank you.
> I am not an expert of Pmems, but my understanding is as follows:
>
> Pmem (Persistent memory) is detected as memory device during boot process.
> Physical addresses are allocated to them just like other memory in DIMM slots,
> so system have to treat them differently from traditional storage devices like HDD/SSD.
>
> It may be technically possible to duplicate data using multiple Pmems, but the duplication
> is practically not useful. For traditional storage devices, you can hot-remove and hot-add
> them easily on failure. However, Pmems are not attached to hot-pluggable slots. You have
> to halt the system and open the cabinet to change out the Pmem. This means availability
> of the system is not improved with data duplication on the same host.
I guess pmem with block translation table type would be fine since it
can be used
like normal storage device, but I am not pmem expert as well 😁.
Thanks,
Guoqing
prev parent reply other threads:[~2023-05-19 10:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 8:21 [PATCH for-next v5 0/7] On-Demand Paging on SoftRoCE Daisuke Matsuda
2023-05-18 8:21 ` [PATCH for-next v5 1/7] RDMA/rxe: Always defer tasks on responder and completer to workqueue Daisuke Matsuda
2023-05-18 8:26 ` Daisuke Matsuda (Fujitsu)
2023-05-18 22:25 ` Bob Pearson
2023-05-18 8:21 ` [PATCH for-next v5 2/7] RDMA/rxe: Make MR functions accessible from other rxe source code Daisuke Matsuda
2023-05-18 22:28 ` Bob Pearson
2023-05-18 8:21 ` [PATCH for-next v5 3/7] RDMA/rxe: Move resp_states definition to rxe_verbs.h Daisuke Matsuda
2023-05-18 22:30 ` Bob Pearson
2023-05-18 8:21 ` [PATCH for-next v5 4/7] RDMA/rxe: Add page invalidation support Daisuke Matsuda
2023-05-19 17:08 ` Bob Pearson
2023-05-18 8:21 ` [PATCH for-next v5 5/7] RDMA/rxe: Allow registering MRs for On-Demand Paging Daisuke Matsuda
2023-05-19 17:09 ` Bob Pearson
2023-06-12 16:18 ` Jason Gunthorpe
2023-07-19 6:00 ` Daisuke Matsuda (Fujitsu)
2023-07-21 18:46 ` Jason Gunthorpe
2023-05-18 8:21 ` [PATCH for-next v5 6/7] RDMA/rxe: Add support for Send/Recv/Write/Read with ODP Daisuke Matsuda
2023-05-19 17:10 ` Bob Pearson
2023-05-19 17:10 ` Bob Pearson
2023-06-12 16:22 ` Jason Gunthorpe
2023-07-19 6:01 ` Daisuke Matsuda (Fujitsu)
2023-09-08 6:35 ` Daisuke Matsuda (Fujitsu)
2023-09-08 13:14 ` Jason Gunthorpe
2023-05-18 8:21 ` [PATCH for-next v5 7/7] RDMA/rxe: Add support for the traditional Atomic operations " Daisuke Matsuda
2023-05-22 18:49 ` Bob Pearson
2023-05-19 6:41 ` [PATCH for-next v5 0/7] On-Demand Paging on SoftRoCE Guoqing Jiang
2023-05-19 9:57 ` Daisuke Matsuda (Fujitsu)
2023-05-19 10:20 ` Guoqing Jiang [this message]
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=e13270a2-c149-6194-b283-06fc38efbd9b@linux.dev \
--to=guoqing.jiang@linux.dev \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=matsuda-daisuke@fujitsu.com \
--cc=rpearsonhpe@gmail.com \
--cc=y-goto@fujitsu.com \
--cc=yangx.jy@fujitsu.com \
--cc=zyjzyj2000@gmail.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.