From: Ric Wheeler <rwheeler@redhat.com>
To: lsf-pc@lists.linuxfoundation.org, linux-fsdevel@vger.kernel.org,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: [LSF/MM TOPIC] update on discard support & testing with vendors
Date: Mon, 17 Jan 2011 09:46:15 -0500 [thread overview]
Message-ID: <4D345637.6000207@redhat.com> (raw)
I would like to spend some time reviewing where we stand with the discard
support - specifically review where we do in the stack (creation time,
fine-grained during deletions, other bulk times), how the options perform and
any performance results we have with various classes of devices (SCSI and SSD).
Similar interest in how the topology/alignment support has worked out.
Both topics took a lot of effort on our part and I expect that we are just now
going to be hitting the point where hardware vendors take us seriously enough &
are starting to test....
Ric
next reply other threads:[~2011-01-17 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 14:46 Ric Wheeler [this message]
2011-01-17 23:18 ` [LSF/MM TOPIC] update on discard support & testing with vendors Mike Snitzer
2011-01-17 23:38 ` Martin K. Petersen
2011-01-18 0:37 ` Matthew Wilcox
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=4D345637.6000207@redhat.com \
--to=rwheeler@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linuxfoundation.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).