From: Mark Lord <kernel@teksavvy.com>
To: Christoph Hellwig <hch@lst.de>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
James.Bottomley@suse.de, snitzer@redhat.com, axboe@kernel.dk,
linux-scsi@vger.kernel.org, dm-devel@redhat.com,
linux-ide@vger.kernel.org
Subject: Re: [RFC 1/2] block: implement an unprep function corresponding directly to prep
Date: Mon, 05 Jul 2010 17:54:43 -0400 [thread overview]
Message-ID: <4C3254A3.6080709@teksavvy.com> (raw)
In-Reply-To: <4C3253C0.8040900@teksavvy.com>
> On 05/07/10 03:24 PM, Christoph Hellwig wrote:
>>
>> What codebase were you testing on? Sorry, but curently I'm a bit lost
>> in the maze of patches. I've got both and intel and an OCZ SSD
..
Do you, or anyone else with one, know what the upper limit is on
TRIM operations with the Intel SSDs ?
I need to know the maximum amount of TRIM ranges they will process
in a single command.
Eg. Indilinx-based SSDs don't appear to have a limit -- they'll accept
a TRIM command with thousands of LBA ranges included.
Sandforce-based SSDs appear to restrict things to max 4KB of range data.
So.. what about Intel?
Thanks
next prev parent reply other threads:[~2010-07-05 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 17:01 [RFC 1/2] block: implement an unprep function corresponding directly to prep James Bottomley
2010-06-30 17:10 ` [RFC 2/2] sd: free discard page in unprep function James Bottomley
2010-06-30 17:23 ` [RFC 1/2] block: implement an unprep function corresponding directly to prep Mike Snitzer
2010-06-30 17:51 ` Jens Axboe
2010-06-30 17:54 ` Martin K. Petersen
2010-07-01 1:47 ` FUJITA Tomonori
2010-07-01 3:47 ` Mike Snitzer
2010-07-01 4:44 ` [dm-devel] " FUJITA Tomonori
2010-07-02 11:03 ` Christoph Hellwig
2010-07-05 7:00 ` FUJITA Tomonori
2010-07-05 19:24 ` Christoph Hellwig
2010-07-05 21:50 ` Mark Lord
2010-07-05 21:54 ` Mark Lord [this message]
2010-07-05 22:00 ` Jeff Garzik
2010-08-03 3:01 ` Mark Lord
2010-07-06 7:04 ` FUJITA Tomonori
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=4C3254A3.6080709@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=James.Bottomley@suse.de \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hch@lst.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=snitzer@redhat.com \
/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