From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ipmail06.adl6.internode.on.net ([150.101.137.145]:37492 "EHLO ipmail06.adl6.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934406AbbKSX3A (ORCPT ); Thu, 19 Nov 2015 18:29:00 -0500 Date: Fri, 20 Nov 2015 10:24:55 +1100 From: Dave Chinner To: Octavian Purdila Cc: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH] xfs: support for non-mmu architectures Message-ID: <20151119232455.GM14311@dastard> References: <1447800381-20167-1-git-send-email-octavian.purdila@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1447800381-20167-1-git-send-email-octavian.purdila@intel.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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.... Cheers, Dave. -- Dave Chinner david@fromorbit.com