All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Octavian Purdila <octavian.purdila@intel.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	xfs@oss.sgi.com
Subject: Re: [RFC PATCH] xfs: support for non-mmu architectures
Date: Fri, 20 Nov 2015 10:24:55 +1100	[thread overview]
Message-ID: <20151119232455.GM14311@dastard> (raw)
In-Reply-To: <1447800381-20167-1-git-send-email-octavian.purdila@intel.com>

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

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Octavian Purdila <octavian.purdila@intel.com>
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
Date: Fri, 20 Nov 2015 10:24:55 +1100	[thread overview]
Message-ID: <20151119232455.GM14311@dastard> (raw)
In-Reply-To: <1447800381-20167-1-git-send-email-octavian.purdila@intel.com>

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

  parent reply	other threads:[~2015-11-19 23:29 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17 22:46 [RFC PATCH] xfs: support for non-mmu architectures Octavian Purdila
2015-11-17 22:46 ` Octavian Purdila
2015-11-19 15:55 ` Brian Foster
2015-11-19 15:55   ` Brian Foster
2015-11-19 20:54   ` Octavian Purdila
2015-11-19 20:54     ` Octavian Purdila
2015-11-20 15:11     ` Brian Foster
2015-11-20 15:11       ` Brian Foster
2015-11-19 23:35   ` Dave Chinner
2015-11-19 23:35     ` Dave Chinner
2015-11-20 14:09     ` Octavian Purdila
2015-11-20 14:09       ` Octavian Purdila
2015-11-20 15:11     ` Brian Foster
2015-11-20 15:11       ` Brian Foster
2015-11-20 15:35       ` Octavian Purdila
2015-11-20 15:35         ` Octavian Purdila
2015-11-20 15:40         ` Brian Foster
2015-11-20 15:40           ` Brian Foster
2015-11-20 20:36       ` Dave Chinner
2015-11-20 20:36         ` Dave Chinner
2015-11-20 22:47         ` Brian Foster
2015-11-20 22:47           ` Brian Foster
2015-11-22 22:04           ` Dave Chinner
2015-11-22 22:04             ` Dave Chinner
2015-11-23 12:50             ` Brian Foster
2015-11-23 12:50               ` Brian Foster
2015-11-23 21:00               ` Dave Chinner
2015-11-23 21:00                 ` Dave Chinner
2015-11-19 23:24 ` Dave Chinner [this message]
2015-11-19 23:24   ` Dave Chinner
2015-11-19 23:54   ` Richard Weinberger
2015-11-19 23:54     ` Richard Weinberger
2015-11-20  0:58     ` Dave Chinner
2015-11-20  0:58       ` Dave Chinner
2015-11-20 14:26       ` Octavian Purdila
2015-11-20 14:26         ` Octavian Purdila
2015-11-20 15:24         ` Brian Foster
2015-11-20 15:24           ` Brian Foster
2015-11-20 15:31           ` Octavian Purdila
2015-11-20 15:31             ` Octavian Purdila
2015-11-20 15:43             ` Brian Foster
2015-11-20 15:43               ` Brian Foster
2015-11-20 20:07         ` Theodore Ts'o
2015-11-20 20:07           ` Theodore Ts'o
2015-11-20 13:43   ` Octavian Purdila
2015-11-20 13:43     ` Octavian Purdila
2015-11-20 21:08     ` Dave Chinner
2015-11-20 21:08       ` Dave Chinner
2015-11-20 22:26       ` Octavian Purdila
2015-11-20 22:26         ` Octavian Purdila
2015-11-22 22:44         ` Dave Chinner
2015-11-22 22:44           ` Dave Chinner
2015-11-23  1:41           ` Octavian Purdila
2015-11-23  1:41             ` Octavian Purdila
2015-11-23 21:46             ` Dave Chinner
2015-11-23 21:46               ` Dave Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151119232455.GM14311@dastard \
    --to=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=octavian.purdila@intel.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.