From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Brian Foster <bfoster@redhat.com>,
Nikolay Borisov <kernel@kyup.com>,
xfs@oss.sgi.com
Subject: Re: Failing XFS memory allocation
Date: Fri, 25 Mar 2016 09:00:21 +1100 [thread overview]
Message-ID: <20160324220021.GF11812@dastard> (raw)
In-Reply-To: <20160324093127.GA4204@infradead.org>
On Thu, Mar 24, 2016 at 02:31:27AM -0700, Christoph Hellwig wrote:
> On Thu, Mar 24, 2016 at 10:00:02AM +1100, Dave Chinner wrote:
> > I'm working on prototype patches to convert it to an in-memory btree
> > but they are far from ready at this point. This isn't straight
> > forward because all the extent management code assumes extents are
> > kept in a linear array and can be directly indexed by array offset
> > rather than file offset. I also want to make sure we can demand page
> > the extent list if necessary, and that also complicates things like
> > locking, as we currently assume the extent list is either completely
> > in memory or not in memory at all.
>
> FYI, I did patches to get rid almost all direct extent array access
> a while ago, but I never bothered to post it as it seemed to much
> churn. Have you started that work yet or would it be useful
> to dust those up again?
I've done bits of it, but haven't completed it - send me the patches
and I'll see which approch makes the most sense...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-03-24 22:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 10:15 Failing XFS memory allocation Nikolay Borisov
2016-03-23 12:43 ` Brian Foster
2016-03-23 12:56 ` Nikolay Borisov
2016-03-23 13:10 ` Brian Foster
2016-03-23 15:03 ` Nikolay Borisov
2016-03-23 16:58 ` Brian Foster
2016-03-23 23:00 ` Dave Chinner
2016-03-24 9:20 ` Nikolay Borisov
2016-03-24 21:58 ` Dave Chinner
2016-03-24 9:31 ` Christoph Hellwig
2016-03-24 22:00 ` Dave Chinner [this message]
2016-03-24 9:33 ` Christoph Hellwig
2016-03-24 9:42 ` Nikolay Borisov
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=20160324220021.GF11812@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=hch@infradead.org \
--cc=kernel@kyup.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox