From: Josef Bacik <jbacik@fusionio.com>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Chris Mason <clmason@fusionio.com>,
Josef Bacik <JBacik@fusionio.com>
Subject: Re: [PATCH RFC] Btrfs: improve delalloc reservation
Date: Wed, 6 Mar 2013 09:07:07 -0500 [thread overview]
Message-ID: <20130306140707.GA1905@localhost.localdomain> (raw)
In-Reply-To: <1362567669-16477-1-git-send-email-bo.li.liu@oracle.com>
On Wed, Mar 06, 2013 at 04:01:09AM -0700, Liu Bo wrote:
> Although we already have over commit stuff, btrfs write performance
> still suffers from over reservation a lot.
>
I'm getting ready to rip all of the reservation code out and put in a ENOSPC log
for a buffer area for delalloc writes and anything outstanding when we run out
of space. This will give us the performance numbers we want and be ENOSPC safe,
we'll stop having early enospc issues and we'll never actually run out of space.
Thanks,
Josef
prev parent reply other threads:[~2013-03-06 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 11:01 [PATCH RFC] Btrfs: improve delalloc reservation Liu Bo
2013-03-06 14:07 ` Josef Bacik [this message]
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=20130306140707.GA1905@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=bo.li.liu@oracle.com \
--cc=clmason@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).