From: Josef Bacik <jbacik@fusionio.com>
To: <linux-btrfs@vger.kernel.org>
Subject: ENOSPC design issues
Date: Thu, 20 Sep 2012 15:03:06 -0400	[thread overview]
Message-ID: <20120920190306.GG2272@localhost.localdomain> (raw)
Hello,
I'm going to look at fixing some of the performance issues that crop up because
of our reservation system.  Before I go and do a whole lot of work I want some
feedback.  I've done a brain dump here
https://btrfs.wiki.kernel.org/index.php/ENOSPC
This has an explanation of how our reservation system currently works and the
problems I think there are with it, and the solutions I'm going to try.  If
somebody has any better ideas please put them on that page along with your IRC
nick so I can find you and we can chat about your idea.  Once we have a few
things we all agree on I'll start hammering away at them.  Some of these things
I'm going to go ahead and do because they are just correct, but the bigger
things such as the flusher thread I'd like some more input on.  Any crazy ideas
welcome, but if your idea involves completely scrapping the current system it
will have to be an awesome idea since I don't really want to spend the next year
fixing early enospc problems again.  Thanks,
Josef
next             reply	other threads:[~2012-09-20 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 19:03 Josef Bacik [this message]
2012-09-24 16:59 ` ENOSPC design issues Mitch Harder
2012-09-25 16:43 ` David Sterba
2012-09-25 17:02   ` Josef Bacik
2012-09-26  7:55     ` Ahmet Inan
2012-09-26 13:00       ` Josef Bacik
2012-09-26 13:11       ` Josef Bacik
2012-09-27 15:39         ` Ahmet Inan
2012-10-01  0:00     ` David Sterba
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=20120920190306.GG2272@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).