From: "Igor Podlesny" <for.poige+linux@gmail.com>
To: linux-raid@vger.kernel.org
Cc: neilb@suse.de
Subject: Re: Hi! I wonder wouldn't it be efficient to select ALGORITHM_?type?_ASYMMETRIC ...
Date: Wed, 12 Nov 2008 01:35:46 +0700 [thread overview]
Message-ID: <43d009740811111035s393c21f6mc4de28b06ec4c741@mail.gmail.com> (raw)
In-Reply-To: <43d009740811051103o504cfb2exef4a5afd1c789801@mail.gmail.com>
Hi!
This letter is re-post primarily for Neil Brown, because no one on
the list had answered that message and Neil's blog says: "If you think
it really needs my attention, Cc me, but still send it to
linux-raid.".
2008/11/6 Igor Podlesny <for.poige+linux@gmail.com>:
> ... depending on, for e. g., chunk number? My assumption is that this
> can address FS meta-data issue, can't it?
>
> (I'm not subscribed to the list, so please CC:.)
>
--
End of message. Next message?
next prev parent reply other threads:[~2008-11-11 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 19:03 Hi! I wonder wouldn't it be efficient to select ALGORITHM_?type?_ASYMMETRIC Igor Podlesny
2008-11-11 18:35 ` Igor Podlesny [this message]
2008-11-11 20:27 ` NeilBrown
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=43d009740811111035s393c21f6mc4de28b06ec4c741@mail.gmail.com \
--to=for.poige+linux@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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