Your message was undeliverable due to the following reason:
Your message was not delivered because the destination computer was
not reachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.
Most likely ther
On Mon, Sep 26, 2016 at 9:16 AM, Elliott, Robert (Persistent Memory)
wrote:
> How is an application supposed to detect the max mmap() size possible
> for a /dev/daxNN device?
The 'size' sysfs attribute.
> fio, for example, doesn't know what size to use. Its os/os-linux.h
> does not define FIO_H
Existing implemenetation writes to all the flush hint addresses for a
given ND region. This is not necessary as the flushes are per imc and
not per DIMM. Search the mappings and clear out the duplicates at init
to avoid multiple flush to the same imc.
Signed-off-by: Dave Jiang
---
drivers/nvdimm
How is an application supposed to detect the max mmap() size possible
for a /dev/daxNN device?
fio, for example, doesn't know what size to use. Its os/os-linux.h
does not define FIO_HAVE_CHARDEV_SIZE and it has no chardev_size
function to determine the size of a character device.
---
Robert Ell
When looking through this patch I've noticed one bug:
On Fri 16-09-16 13:27:14, Christoph Hellwig wrote:
> +static int ext2_iomap_begin(struct inode *inode, loff_t offset, loff_t
> length,
> + unsigned flags, struct iomap *iomap)
> +{
...
> + iomap->offset = first_block << blkbits
On Mon 26-09-16 02:08:05, Christoph Hellwig wrote:
> On Fri, Sep 23, 2016 at 03:02:37PM -0600, Ross Zwisler wrote:
> > I can just add a hack to hop over the writeback in generic_file_read_iter(),
> > but I hesitate to do this because it seems like the correct thing to do is
> > to
> > separate the
