On Fri, Nov 20, 2015 at 1:24 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote: > On Wed, Nov 18, 2015 at 12:46:21AM +0200, Octavian Purdila wrote: >> Naive implementation for non-mmu architectures: allocate physically >> contiguous xfs buffers with alloc_pages. Terribly inefficient with >> memory and fragmentation on high I/O loads but it may be good enough >> for basic usage (which most non-mmu architectures will need). > > Can you please explain why you want to use XFS on low end, basic > non-MMU devices? XFS is a high performance, enterprise/HPC level > filesystem - it's not a filesystem designed for small IoT level > devices - so I'm struggling to see why we'd want to expend any > effort to make XFS work on such devices.... > Hi David, Yes XFS as the main fs on this type of devices does not make sense, but does it hurt to be able to perform basic operation on XFS from these devices? Perhaps accessing an external medium formatted with XFS? Another example is accessing VM images that are formatted with XFS. Currently we can do that with tools like libguestfs that use a VM in the background. I am working on a lighter solution for that where we compile the Linux kernel as a library [1]. This allows access to the filesystem without the need to use a full VM. And a final example is linking the bootloader code with LKL to access the filesystem. This has a hard requirement on non-mmu. So, IMHO there are usecases for using XFS on non-mmu architectures. I think it all boils down to: is the patch simple enough to not put an unreasonable maintenance burden on developers? [1] https://github.com/lkl/linux Thanks, Tavi -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
