On Sun, Sep 9, 2018 at 11:21 PM, Ocean He wrote:
> From: Ocean He
>
> When pmem namespaces created are smaller than section size twice, the
> second creation would fail and meanwhile there is a kernel call trace
> which comes from commit 15d36fecd0bdc7510b70 ("mm: disallow mappings that
>
Hi Ocean,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linux-nvdimm/libnvdimm-for-next]
[also build test WARNING on v4.19-rc3 next-20180910]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
Fixes: 39ac5d361db2 ("libnvdimm, region_devs: reset related seeds when fail to
create namespace")
Signed-off-by: kbuild test robot
---
region_devs.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvdimm/region_devs.c b/drivers/nvdimm/region_devs.c
index
On Mon, Sep 10, 2018 at 4:44 PM Alexander Duyck
wrote:
>
> From: Alexander Duyck
>
> This patch is based off of the pci_call_probe function used to initialize
> PCI devices. The general idea here is to move the probe call to a location
> that is local to the memory being initialized. By doing
On Mon, Sep 10, 2018 at 4:43 PM Alexander Duyck
wrote:
>
> From: Alexander Duyck
>
> On systems with a large amount of memory it can take a significant amount
> of time to initialize all of the page structs with the PAGE_POISON_PATTERN
> value. I have seen it take over 2 minutes to initialize a
From: Alexander Duyck
On systems with a large amount of memory it can take a significant amount
of time to initialize all of the page structs with the PAGE_POISON_PATTERN
value. I have seen it take over 2 minutes to initialize a system with
over 12GB of RAM.
In order to work around the issue I
From: Alexander Duyck
It doesn't make much sense to use the atomic SetPageReserved at init time
when we are using memset to clear the memory and manipulating the page
flags via simple "&=" and "|=" operations in __init_single_page.
This patch adds a non-atomic version __SetPageReserved that can
From: Alexander Duyck
The ZONE_DEVICE pages were being initialized in two locations. One was with
the memory_hotplug lock held and another was outside of that lock. The
problem with this is that it was nearly doubling the memory initialization
time. Instead of doing this twice, once while
This patch set is meant to be a v3 to my earlier patch set "Address issues
slowing memory init"[1]. However I have added 2 additional patches to
address issues seen in which NVDIMM memory was slow to initialize
especially on systems with multiple NUMA nodes.
Since v2 of the patch set I have
With address_space_operations missing for device dax, namely the
.set_page_dirty, we hit a kernel warning when running destructive
ndctl unit test: make TESTS=device-dax check
WARNING: CPU: 3 PID: 7380 at fs/buffer.c:581 __set_page_dirty+0xb1/0xc0
Setting address_space_operations to
On 8/7/18 3:45 AM, Jan Kara wrote:
> On Fri 27-07-18 10:28:51, Ross Zwisler wrote:
>> + fsdevel and the xfs list.
>>
>> On Wed, Jul 25, 2018 at 4:28 PM Ross Zwisler
>> wrote:
>>> On Wed, Jul 11, 2018 at 10:17:41AM +0200, Jan Kara wrote:
On Tue 10-07-18 13:10:29, Ross Zwisler wrote:
>
On Mon, Sep 10, 2018 at 12:06 PM Dan Williams wrote:
>
> [ adding Alex ]
>
> On Tue, Jul 24, 2018 at 12:29 AM, Michal Hocko wrote:
> > On Mon 23-07-18 09:15:32, Dave Hansen wrote:
> >> On 07/23/2018 04:09 AM, Michal Hocko wrote:
> >> > On Thu 19-07-18 11:41:10, Dave Hansen wrote:
> >> >> Are you
[ adding Alex ]
On Tue, Jul 24, 2018 at 12:29 AM, Michal Hocko wrote:
> On Mon 23-07-18 09:15:32, Dave Hansen wrote:
>> On 07/23/2018 04:09 AM, Michal Hocko wrote:
>> > On Thu 19-07-18 11:41:10, Dave Hansen wrote:
>> >> Are you looking for the actual end-user reports? This was more of a
>> >>
On 10/09/18 10:41 AM, Christoph Hellwig wrote:
> On Wed, Sep 05, 2018 at 03:03:18PM -0600, Logan Gunthorpe wrote:
>> There is no special p2p submission process. In the nvme-of case we are
>> using the existing process and with the code in blk-core it didn't
>> change it's process at all.
> -Original Message-
> From: Linux-nvdimm [mailto:linux-nvdimm-boun...@lists.01.org] On Behalf Of
> Kani, Toshi
> Sent: Monday, September 10, 2018 9:52 AM
> To: j...@suse.cz
> Cc: linux-fsde...@vger.kernel.org; linux-nvdimm@lists.01.org
> Subject: Re: open sets ext4_da_aops for DAX
On Wed, Sep 05, 2018 at 03:03:18PM -0600, Logan Gunthorpe wrote:
> There is no special p2p submission process. In the nvme-of case we are
> using the existing process and with the code in blk-core it didn't
> change it's process at all. Creating a helper will create one and I can
> look at making
On 8/8/18 12:25 PM, Dave Jiang wrote:
> From: Ross Zwisler
>
> If the refcount of a page is lowered between the time that it is returned
> by dax_busy_page() and when the refcount is again checked in
> ext4_break_layouts() => ___wait_var_event(), the waiting function
> ext4_wait_dax_page() will
On Fri 07-09-18 21:23:19, Kani, Toshi wrote:
> I noticed that both ext4_da_aops and ext4_dax_aops are used on DAX
> mounted ext4 files. Looking at open() path:
>
> New file
>
> lookup_open
> ext4_create
> __ext4_new_inode
> ext4_set_inode_flags // Set S_DAX flag
>
On Mon, Sep 10, 2018 at 7:21 AM, Kani, Toshi wrote:
> On Mon, 2018-09-10 at 08:54 -0400, Jeff Moyer wrote:
>> "Kani, Toshi" writes:
>>
>> > I noticed that both ext4_da_aops and ext4_dax_aops are used on DAX
>> > mounted ext4 files. Looking at open() path:
>>
>> Eek. How did you notice this?
>
On Mon, 2018-09-10 at 08:54 -0400, Jeff Moyer wrote:
> "Kani, Toshi" writes:
>
> > I noticed that both ext4_da_aops and ext4_dax_aops are used on DAX
> > mounted ext4 files. Looking at open() path:
>
> Eek. How did you notice this?
I tested sync path on DAX files to see if it flushes
"Kani, Toshi" writes:
> I noticed that both ext4_da_aops and ext4_dax_aops are used on DAX
> mounted ext4 files. Looking at open() path:
Eek. How did you notice this?
-Jeff
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
Please confirm your email address
Dear Valid user,
We are undergoing maintenance therefore all accounts must be updated to avoid
suspension, this is to reduce the number of dormant accounts.
Failure to this
From: Ocean He
During runtime, if a namespace seed is used for new namespace creation
but fail, then it needs to be reset for next namespace creation.
Add function nd_region_reset_ns_seed for namespace seed reset and
declare it in nd-core.h.
Signed-off-by: Ocean He
---
From: Ocean He
During runtime, namespace creation may fail if blocked by
commit 15d36fecd0bdc7510b70 ("mm: disallow mappings that conflict for
devm_memremap_pages()"). To ensure pfn_seed/dax_seed and namespace_seed
are ready for next namespace creation, here to do detach and reset.
From: Ocean He
The function nd_detach_and_reset needs to be called externally, so
remove the static attribute and declare it in nd-core.h.
Signed-off-by: Ocean He
---
drivers/nvdimm/claim.c | 2 +-
drivers/nvdimm/nd-core.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git
From: Ocean He
When pmem namespaces created are smaller than section size twice, the
second creation would fail and meanwhile there is a kernel call trace
which comes from commit 15d36fecd0bdc7510b70 ("mm: disallow mappings that
conflict for devm_memremap_pages()").
[ cut
26 matches
Mail list logo
