On 24/05/23 03:57PM, Miklos Szeredi wrote:
> [trimming CC list]
>
> On Thu, 23 May 2024 at 04:49, John Groves wrote:
>
> > - memmap=! will reserve a pretend pmem device at
> >
> > - memmap=$ will reserve a pretend dax device at
> >
>
> Doesn'
On 24/05/23 03:57PM, Miklos Szeredi wrote:
> [trimming CC list]
>
> On Thu, 23 May 2024 at 04:49, John Groves wrote:
>
> > - memmap=! will reserve a pretend pmem device at
> >
> > - memmap=$ will reserve a pretend dax device at
> >
>
> Doesn'
From: John Groves
Add CONFIG_DEV_DAXIOMAP kernel build parameter
---
drivers/dax/Kconfig | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/dax/Kconfig b/drivers/dax/Kconfig
index a88744244149..b1ebcc77120b 100644
--- a/drivers/dax/Kconfig
+++ b/drivers/dax/Kconfig
@@ -78,4
From: John Groves
This is the primary content of this rfc. Notes about this commit:
* These methods are based somewhat loosely on pmem_dax_ops from
drivers/nvdimm/pmem.c
* dev_dax_direct_access() is physaddr based
* dev_dax_direct_access() works for mmap, but fails dax_copy_to_iter()
on
From: John Groves
These are functions that should be called from outside, but I had
linkage issues and did this hack instead. Will fix in the "real"
patches...
---
drivers/dax/bus.c | 50 +++
1 file changed, 50 insertions(+)
diff --git a/d
From: John Groves
This is clearly not the right way to set the holder_ops; where &
how should this be done?
---
drivers/dax/super.c | 16
include/linux/dax.h | 5 +
2 files changed, 21 insertions(+)
diff --git a/drivers/dax/super.c b/drivers/dax/super.c
index 0da9232e
From: John Groves
This patch set is not intended to be merged; I'm hoping to get some
clarification as to the correct approach (especialy from Dan).
This work is related to famfs, which is a dax file system for shared
fabric-attached memory (FAM). Famfs is "coming soon" as
7 matches
Mail list logo
