转发:精益生产-天津丰田、北京奔驰考察班

2017-08-15 Thread 葛竞
附件 大纲 ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm

Re: [PATCH v2 0/5] fs, xfs: block map immutable files for dax, dma-to-storage, and swap

2017-08-15 Thread Jan Kara
On Mon 14-08-17 09:14:42, Dan Williams wrote: > On Mon, Aug 14, 2017 at 5:40 AM, Jan Kara wrote: > > On Sun 13-08-17 13:31:45, Dan Williams wrote: > >> On Sun, Aug 13, 2017 at 2:24 AM, Christoph Hellwig wrote: > >> > Thay being said I think we absolutely should support RDMA memory > >> > registra

Re: [PATCH v4 0/3] MAP_DIRECT and block-map sealed files

2017-08-15 Thread Dave Chinner
On Mon, Aug 14, 2017 at 11:12:05PM -0700, Dan Williams wrote: > Changes since v3 [1]: > * Move from an fallocate(2) interface to a new mmap(2) flag and rename > 'immutable' to 'sealed'. > > * Do not record the sealed state in permanent metadata it is now purely > a temporary state for as long

Re: [RFC PATCH 0/7] dax, ext4: Synchronous page faults

2017-08-15 Thread Boaz Harrosh
On 14/08/17 19:03, Dan Williams wrote: > On Mon, Aug 14, 2017 at 7:04 AM, Boaz Harrosh wrote: >> >> Thank you Jan, I'm patiently waiting for this MAP_SYNC flag since I asked for >> it in 2014. I'm so glad its time is finally do. >> <> >> 4] Once we have this flag. And properly implemented at lea

Re: [PATCH v4 3/3] fs, xfs: introduce MAP_DIRECT for creating block-map-sealed file ranges

2017-08-15 Thread Kirill A. Shutemov
On Mon, Aug 14, 2017 at 11:12:22PM -0700, Dan Williams wrote: > MAP_DIRECT is an mmap(2) flag with the following semantics: > > MAP_DIRECT > In addition to this mapping having MAP_SHARED semantics, successful > faults in this range may assume that the block map (logical-file-offset > to ph

Re: [RFC PATCH 0/7] dax, ext4: Synchronous page faults

2017-08-15 Thread Boaz Harrosh
On 15/08/17 12:06, Boaz Harrosh wrote: > On 14/08/17 19:03, Dan Williams wrote: >> On Mon, Aug 14, 2017 at 7:04 AM, Boaz Harrosh wrote: >>> >>> Thank you Jan, I'm patiently waiting for this MAP_SYNC flag since I asked >>> for >>> it in 2014. I'm so glad its time is finally do. >>> > > <> > >>>

Re: [PATCH v4 2/3] mm: introduce MAP_VALIDATE a mechanism for adding new mmap flags

2017-08-15 Thread Jan Kara
On Mon 14-08-17 23:12:16, Dan Williams wrote: > The mmap syscall suffers from the ABI anti-pattern of not validating > unknown flags. However, proposals like MAP_SYNC and MAP_DIRECT need a > mechanism to define new behavior that is known to fail on older kernels > without the feature. Use the fact

Re: [PATCH v4 3/3] fs, xfs: introduce MAP_DIRECT for creating block-map-sealed file ranges

2017-08-15 Thread Jan Kara
On Mon 14-08-17 23:12:22, Dan Williams wrote: > diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h > index ff151814a02d..73fdc0ada9ee 100644 > --- a/include/linux/mm_types.h > +++ b/include/linux/mm_types.h > @@ -306,6 +306,7 @@ struct vm_area_struct { > struct mm_struct *vm_mm;

Re: [PATCH 2/3] libnvdimm, pfn, dax: show supported dax/pfn region alignments in sysfs

2017-08-15 Thread Dan Williams
On Mon, Aug 14, 2017 at 11:46 PM, Oliver wrote: > On Tue, Aug 15, 2017 at 4:02 PM, kbuild test robot wrote: [..] >>114 static const unsigned long *nd_pfn_supported_alignments(void) >>115 { >>116 /* >>117 * This needs to be a local variable because the *_SIZE

Re: [PATCH v4 2/3] mm: introduce MAP_VALIDATE a mechanism for adding new mmap flags

2017-08-15 Thread Dan Williams
On Tue, Aug 15, 2017 at 5:27 AM, Jan Kara wrote: > On Mon 14-08-17 23:12:16, Dan Williams wrote: >> The mmap syscall suffers from the ABI anti-pattern of not validating >> unknown flags. However, proposals like MAP_SYNC and MAP_DIRECT need a >> mechanism to define new behavior that is known to fai

Re: [PATCH v4 2/3] mm: introduce MAP_VALIDATE a mechanism for adding new mmap flags

2017-08-15 Thread Andy Lutomirski
On Mon, Aug 14, 2017 at 11:12 PM, Dan Williams wrote: > The mmap syscall suffers from the ABI anti-pattern of not validating > unknown flags. However, proposals like MAP_SYNC and MAP_DIRECT need a > mechanism to define new behavior that is known to fail on older kernels > without the feature. Use

Re: [PATCH v4 3/3] fs, xfs: introduce MAP_DIRECT for creating block-map-sealed file ranges

2017-08-15 Thread Dan Williams
On Tue, Aug 15, 2017 at 5:42 AM, Jan Kara wrote: > On Mon 14-08-17 23:12:22, Dan Williams wrote: >> diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h >> index ff151814a02d..73fdc0ada9ee 100644 >> --- a/include/linux/mm_types.h >> +++ b/include/linux/mm_types.h >> @@ -306,6 +306,7 @@

Re: [PATCH v4 3/3] fs, xfs: introduce MAP_DIRECT for creating block-map-sealed file ranges

2017-08-15 Thread Dan Williams
On Tue, Aug 15, 2017 at 2:18 AM, Kirill A. Shutemov wrote: > On Mon, Aug 14, 2017 at 11:12:22PM -0700, Dan Williams wrote: >> MAP_DIRECT is an mmap(2) flag with the following semantics: >> >> MAP_DIRECT >> In addition to this mapping having MAP_SHARED semantics, successful >> faults in this

get_user_pages_unlocked() fails for mmap()-ed nvdimm-backed file

2017-08-15 Thread Honda Michio
Dear Linux NVDIMM developers, We are implementing a kernel module that get_user_pages()s an address provided by a user-space application. This address is a mmap()-ed region of a file backed by pmem (XFS with DAX). It works or successfully gets a kernel virtual address for emulated PMEM with memmap

Re: get_user_pages_unlocked() fails for mmap()-ed nvdimm-backed file

2017-08-15 Thread Dan Williams
On Tue, Aug 15, 2017 at 2:56 PM, Honda Michio wrote: > Dear Linux NVDIMM developers, > > We are implementing a kernel module that get_user_pages()s an address > provided by a user-space application. This address is a mmap()-ed region of > a file backed by pmem (XFS with DAX). > It works or success

Re: [PATCH v4 2/3] mm: introduce MAP_VALIDATE a mechanism for adding new mmap flags

2017-08-15 Thread Dan Williams
On Tue, Aug 15, 2017 at 9:28 AM, Andy Lutomirski wrote: > On Mon, Aug 14, 2017 at 11:12 PM, Dan Williams > wrote: >> The mmap syscall suffers from the ABI anti-pattern of not validating >> unknown flags. However, proposals like MAP_SYNC and MAP_DIRECT need a >> mechanism to define new behavior t

Re: [PATCH v2 0/5] fs, xfs: block map immutable files for dax, dma-to-storage, and swap

2017-08-15 Thread Dan Williams
On Tue, Aug 15, 2017 at 1:37 AM, Jan Kara wrote: > On Mon 14-08-17 09:14:42, Dan Williams wrote: >> On Mon, Aug 14, 2017 at 5:40 AM, Jan Kara wrote: >> > On Sun 13-08-17 13:31:45, Dan Williams wrote: >> >> On Sun, Aug 13, 2017 at 2:24 AM, Christoph Hellwig wrote: >> >> > Thay being said I think

Re: [PATCH v4 3/3] fs, xfs: introduce MAP_DIRECT for creating block-map-sealed file ranges

2017-08-15 Thread Dan Williams
On Tue, Aug 15, 2017 at 9:29 AM, Dan Williams wrote: > On Tue, Aug 15, 2017 at 5:42 AM, Jan Kara wrote: >> On Mon 14-08-17 23:12:22, Dan Williams wrote: >>> diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h >>> index ff151814a02d..73fdc0ada9ee 100644 >>> --- a/include/linux/mm_type

回复:研 发 质 量 管 理 六 根 基

2017-08-15 Thread 刁仆
___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm

Re: Daemon of NVDIMM event notification/monitoring(Re: Standardization of ACPI NVDIMM DSMs)

2017-08-15 Thread Yasunori Goto
> > >> Another approach could be to integrate NVDIMM event > >> monitoring into some other utility, like the rasdaemon. I'm > >> interested in > >> your thoughts. > > > > Though I'm not sure which (existing or new) utility is appropriate yet. > > I prefer this

Re: get_user_pages_unlocked() fails for mmap()-ed nvdimm-backed file

2017-08-15 Thread Michio Honda
You were right and it perfectly works now (I used "pending" branch of ndctl). Thanks a lot! Cheers, - Michio On 08/16/2017 12:05 AM, Dan Williams wrote: On Tue, Aug 15, 2017 at 2:56 PM, Honda Michio wrote: Dear Linux NVDIMM developers, We are implementing a kernel module that get_user_pages

Re: [PATCH v1 2/6] fs: use on-stack-bio if backing device has BDI_CAP_SYNC capability

2017-08-15 Thread Minchan Kim
Hi Jens, On Mon, Aug 14, 2017 at 10:17:09AM -0600, Jens Axboe wrote: > On 08/14/2017 09:38 AM, Jens Axboe wrote: > > On 08/14/2017 09:31 AM, Minchan Kim wrote: > >>> Secondly, generally you don't have slow devices and fast devices > >>> intermingled when running workloads. That's the rare case. >

Re: [PATCH 2/3] libnvdimm, pfn, dax: show supported dax/pfn region alignments in sysfs

2017-08-15 Thread Oliver
On Wed, Aug 16, 2017 at 1:47 AM, Dan Williams wrote: > On Mon, Aug 14, 2017 at 11:46 PM, Oliver wrote: >> On Tue, Aug 15, 2017 at 4:02 PM, kbuild test robot wrote: > [..] >>>114 static const unsigned long *nd_pfn_supported_alignments(void) >>>115 { >>>116 /* >>>117