/get/ fsdax
>>>> mode these days?" this morning]
>>>>
>>>> On Tue, Oct 25, 2022 at 10:56:19AM -0700, Darrick J. Wong wrote:
>>>>> On Tue, Oct 25, 2022 at 02:26:50PM +, ruansy.f...@fujitsu.com wrote:
>>
>> ...skip...
>>
>>&g
在 2022/10/24 13:31, Dave Chinner 写道:
> On Mon, Oct 24, 2022 at 03:17:52AM +0000, ruansy.f...@fujitsu.com wrote:
>> 在 2022/10/24 6:00, Dave Chinner 写道:
>>> On Fri, Oct 21, 2022 at 07:11:02PM -0700, Darrick J. Wong wrote:
>>>> On Thu, Oct 20, 2022 at 10:17:45
file for now. */
if ((fa->fsx_xflags & FS_XFLAG_DAX) && xfs_is_reflink_inode(ip))
return -EINVAL;
b. fs/xfs/xfs_iops.c:1174
/* Only supported on non-reflinked files. */
if (xfs_is_reflink_inode(ip))
return false;
These restrictions were removed in "drop experimental warning" pat
> From: Jane Chu
> Subject: Re: [PATCH RESEND v6 1/9] pagemap: Introduce ->memory_failure()
>
> Sorry, correction in line.
>
> On 8/19/2021 12:18 AM, Jane Chu wrote:
> > Hi, Shiyang,
> >
> > > > > 1) What does it take and cost to make > > >
> > xfs_sb_version_hasrmapbt(>m_sb) to return
> -Original Message-
> From: Jane Chu
> Subject: Re: [PATCH RESEND v6 1/9] pagemap: Introduce ->memory_failure()
>
>
> On 8/17/2021 10:43 PM, Jane Chu wrote:
> > More information -
> >
> > On 8/16/2021 10:20 AM, Jane Chu wrote:
> >> Hi, ShiYang,
> >>
> >> So I applied the v6 patch
> -Original Message-
> From: Jane Chu
> Subject: Re: [PATCH RESEND v6 8/9] md: Implement dax_holder_operations
>
> On 7/30/2021 3:01 AM, Shiyang Ruan wrote:
> > This is the case where the holder represents a mapped device, or a
> > list of mapped devices more exactly(because it is
> -Original Message-
> From: Jane Chu
> Subject: Re: [PATCH RESEND v6 2/9] dax: Introduce holder for dax_device
>
>
> On 7/30/2021 3:01 AM, Shiyang Ruan wrote:
> > --- a/drivers/dax/super.c
> > +++ b/drivers/dax/super.c
> > @@ -214,6 +214,8 @@ enum dax_device_flags {
> >* @cdev:
> -Original Message-
> From: Jane Chu
> Subject: Re: [PATCH RESEND v6 1/9] pagemap: Introduce ->memory_failure()
>
> Hi, ShiYang,
>
> So I applied the v6 patch series to my 5.14-rc3 as it's what you indicated is
> what
> v6 was based at, and injected a hardware poison.
>
> I'm seeing
> -Original Message-
> Subject: Re: [PATCH v6 6/9] xfs: Implement ->corrupted_range() for XFS
>
> There is no ocurrence of "corrupted_range" in this patch. Does the patch
> subject need updating?
>
Yes, I forgot this... Thanks for pointing out.
--
Thanks,
Ruan.
>
> On 30.07.21
> -Original Message-
> Subject: Re: [PATCH v5 2/9] dax: Introduce holder for dax_device
>
> On Mon, Jun 28, 2021 at 08:02:11AM +0800, Shiyang Ruan wrote:
> > +int dax_holder_notify_failure(struct dax_device *dax_dev, loff_t offset,
> > + size_t size, void *data)
>
> From: Matthew Wilcox
> Subject: Re: [PATCH v5 5/9] mm: Introduce mf_dax_kill_procs() for fsdax case
>
> On Tue, Jun 29, 2021 at 07:49:24AM +0000, ruansy.f...@fujitsu.com wrote:
> > > But I think this is unnecessary; why not just pass the PFN into
> mf_dax_kil
> -Original Message-
> From: Matthew Wilcox
> Subject: Re: [PATCH v5 5/9] mm: Introduce mf_dax_kill_procs() for fsdax case
>
> On Mon, Jun 28, 2021 at 08:02:14AM +0800, Shiyang Ruan wrote:
> > +/*
> > + * dax_load_pfn - Load pfn of the DAX entry corresponding to a page
> > + *
> -Original Message-
> From: Dan Williams
> Subject: Re: [PATCH v4 03/10] fs: Introduce ->corrupted_range() for superblock
>
> On Wed, Jun 16, 2021 at 11:51 PM ruansy.f...@fujitsu.com
> wrote:
> >
> > > -Original Message-
> > > From:
> -Original Message-
> From: Dan Williams
> Subject: Re: [PATCH v4 04/10] mm, fsdax: Refactor memory-failure handler for
> dax mapping
>
> [ drop old nvdimm list, add the new one ]
>
> On Thu, Jun 3, 2021 at 6:19 PM Shiyang Ruan wrote:
> >
> > The current memory_failure_dev_pagemap()
> -Original Message-
> From: Dan Williams
> Subject: Re: [PATCH v4 03/10] fs: Introduce ->corrupted_range() for superblock
>
> [ drop old linux-nvd...@lists.01.org, add nvd...@lists.linux.dev ]
>
> On Thu, Jun 3, 2021 at 6:19 PM Shiyang Ruan wrote:
> >
> > Memory failure occurs in
> -Original Message-
> From: ruansy.f...@fujitsu.com
> Subject: RE: [PATCH v3 01/11] pagemap: Introduce ->memory_failure()
> > > > > >
> > > > > > After the conversation with Dave I don't see the point of this.
> > > > >
> -Original Message-
> From: zhong jiang
> Subject: Re: [PATCH v3 05/11] mm, fsdax: Refactor memory-failure handler for
> dax mapping
>
> > +int mf_dax_mapping_kill_procs(struct address_space *mapping, pgoff_t
> > +index, int flags) {
> > + const bool unmap_success = true;
> > +
> -Original Message-
> From: Dan Williams
> Subject: Re: [PATCH v3 01/11] pagemap: Introduce ->memory_failure()
>
> On Mon, Mar 8, 2021 at 3:34 AM ruansy.f...@fujitsu.com
> wrote:
> > > > > > 1 file changed, 8 insertions(+)
> > &
> > > > 1 file changed, 8 insertions(+)
> > > >
> > > > diff --git a/include/linux/memremap.h b/include/linux/memremap.h
> > > > index 79c49e7f5c30..0bcf2b1e20bd 100644
> > > > --- a/include/linux/memremap.h
> > > > +++ b/include/linux/memremap.h
> > > > @@ -87,6 +87,14 @@ struct dev_pagemap_ops
> On Mon, Feb 8, 2021 at 2:55 AM Shiyang Ruan
> wrote:
> >
> > When memory-failure occurs, we call this function which is implemented
> > by each kind of devices. For the fsdax case, pmem device driver
> > implements it. Pmem device driver will find out the block device where
> > the error
20 matches
Mail list logo
