From: Jeff Moyer <jmoyer@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] dio: add a mempool for the unaligned block structures
Date: Mon, 08 Nov 2010 10:40:37 -0500 [thread overview]
Message-ID: <x49wron962y.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <1289202023-15102-4-git-send-email-david@fromorbit.com> (Dave Chinner's message of "Mon, 8 Nov 2010 18:40:23 +1100")
Dave Chinner <david@fromorbit.com> writes:
> From: Dave Chinner <dchinner@redhat.com>
>
> We need the zero block tracking structure allocation to succeed.
> Silently failing and potentially allowing data corruption is not an
> option. Add a mempool to ensure this allocation will always succeed.
>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
Acked-by: Jeff Moyer <jmoyer@redhat.com>
next prev parent reply other threads:[~2010-11-08 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 7:40 [REPOST, PATCH 0/3] dio: serialise unaligned direct IO Dave Chinner
2010-11-08 7:40 ` [PATCH 1/3] dio: track and " Dave Chinner
2010-11-08 15:28 ` Jeff Moyer
2010-11-08 22:55 ` Dave Chinner
2010-11-08 7:40 ` [PATCH 2/3] dio: scale unaligned IO tracking via multiple lists Dave Chinner
2010-11-08 15:36 ` Jeff Moyer
2010-11-08 23:12 ` Dave Chinner
2010-11-09 21:04 ` Jeff Moyer
2010-11-09 23:06 ` Dave Chinner
2010-11-11 15:32 ` Jeff Moyer
2010-11-08 7:40 ` [PATCH 3/3] dio: add a mempool for the unaligned block structures Dave Chinner
2010-11-08 15:40 ` Jeff Moyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-03 7:23 [PATCH 0/3] dio: serialise unaligned direct IO V3 Dave Chinner
2010-08-03 7:23 ` [PATCH 3/3] dio: add a mempool for the unaligned block structures 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=x49wron962y.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).