Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934889AbbKSXyG (ORCPT ); Thu, 19 Nov 2015 18:54:06 -0500 Received: from mail-ob0-f179.google.com ([209.85.214.179]:36666 "EHLO mail-ob0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759412AbbKSXyD (ORCPT ); Thu, 19 Nov 2015 18:54:03 -0500 MIME-Version: 1.0 In-Reply-To: <20151119232455.GM14311@dastard> References: <1447800381-20167-1-git-send-email-octavian.purdila@intel.com> <20151119232455.GM14311@dastard> Date: Fri, 20 Nov 2015 00:54:02 +0100 Message-ID: Subject: Re: [RFC PATCH] xfs: support for non-mmu architectures From: Richard Weinberger To: Dave Chinner Cc: Octavian Purdila , xfs , linux-fsdevel , LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1162 Lines: 27 On Fri, Nov 20, 2015 at 12:24 AM, Dave Chinner 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.... The use case is the Linux Kernel Library: https://lkml.org/lkml/2015/11/3/706 Using LKL and fuse you can mount any kernel filesystem using fuse as non-root. -- Thanks, //richard -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/