From: DagB <dag@bakke.com>
To: linux-lvm@redhat.com, linux-raid@vger.kernel.org, dm-devel@redhat.com
Subject: Re: raid0 and discard/trim - current state?
Date: Sat, 09 Oct 2010 20:34:33 +0200 [thread overview]
Message-ID: <4CB0B5B9.8070409@bakke.com> (raw)
In-Reply-To: <4CB0A4B5.4010009@bakke.com>
On 10/09/2010 07:21 PM, DagB wrote:
> Hi.
>
> I wonder about the current state of affairs regarding striping over
> multiple SSDs.
>
> Found this thread:
> http://marc.info/?t=126787186000002&r=1&w=2
>
> but nothing after that. Was this problem to hard to handle?
>
Bad form to reply to self.
More googling finally turned up this commit:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8357422d4bf33bc2c35884d4016c3fc9efbbc1d2
So I'll be ordering 2 SSDs.
Dag B
next prev parent reply other threads:[~2010-10-09 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 17:21 raid0 and discard/trim - current state? DagB
2010-10-09 18:34 ` DagB [this message]
2010-10-12 20:57 ` Mike Snitzer
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=4CB0B5B9.8070409@bakke.com \
--to=dag@bakke.com \
--cc=dm-devel@redhat.com \
--cc=linux-lvm@redhat.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).