On Mon, Sep 26, 2016 at 9:16 AM, Elliott, Robert (Persistent Memory) <[email protected]> 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_HAVE_CHARDEV_SIZE and it has no chardev_size > function to determine the size of a character device. Hmm, seems fio would do the right thing if /dev/dax responded to block device size ioctl. But I think I'd rather teach fio about device-dax explicitly since the i/o engine need not worry about page-cache management. _______________________________________________ Linux-nvdimm mailing list [email protected] https://lists.01.org/mailman/listinfo/linux-nvdimm
