From: Josef Bacik <josef@redhat.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: ENOSPC overhaul
Date: Tue, 26 Jul 2011 14:13:51 -0400 [thread overview]
Message-ID: <4E2F03DF.9030302@redhat.com> (raw)
Hello,
I'm going to be going through our ENOSPC handling to make it simpler and
fixing the various performance problems and too early problems we have
been seeing. I'm going to target these for 3.2, but I'm going to post
them as I churn them out so people can review them and test them.
Please respond to this email with your pet-ENOSPC test, I want to make
sure we are in good standing when the merge window opens for 3.2 so we
don't ever have to worry about this problem again (at least in the big
general sense that we have had to in the past). Thanks,
Josef
reply other threads:[~2011-07-26 18:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E2F03DF.9030302@redhat.com \
--to=josef@redhat.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).