From: NeilBrown <neilb@suse.de>
To: for.poige+linux@gmail.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Hi! Is "container" more efficient in terms of I/O op. numbers ...
Date: Fri, 25 May 2012 10:14:24 +1000 [thread overview]
Message-ID: <20120525101424.3cb40eb2@notabene.brown> (raw)
In-Reply-To: <CA+sTkh55N8YKL5R-a70U9jYrj17hAdLbSoKPy-Xuz2-2S5_P0g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 304 bytes --]
On Thu, 24 May 2012 23:30:54 +0800 Igor Podlesny <for.poige+linux@gmail.com>
wrote:
> ... then several "stand-alone" RAIDs on the same HDDs? -- Say, when
> using write intent bitmaps.
>
I'm not sure you question exactly makes sense, but the answer would be "no"
if it did :-)
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-05-25 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 15:30 Hi! Is "container" more efficient in terms of I/O op. numbers Igor Podlesny
2012-05-25 0:14 ` NeilBrown [this message]
2012-05-25 1:52 ` Igor Podlesny
2012-05-25 2:23 ` NeilBrown
2012-05-25 2:41 ` Igor Podlesny
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=20120525101424.3cb40eb2@notabene.brown \
--to=neilb@suse.de \
--cc=for.poige+linux@gmail.com \
--cc=linux-raid@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).