From: Chris Samuel <chris@csamuel.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: tj@kernel.org, linux-ide@vger.kernel.org, Marc MERLIN <marc@merlins.org>
Subject: Re: [PATCH 1/2] libata: Expose trim capability in sysfs
Date: Sat, 05 Apr 2014 08:49:45 +1100 [thread overview]
Message-ID: <7474970.Ep9zfmpRio@quad> (raw)
In-Reply-To: <1396399357-28388-1-git-send-email-martin.petersen@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
On Tue, 1 Apr 2014 08:42:36 PM Martin K. Petersen wrote:
> Now that drives with support for queued trim are starting to appear, it
> would be helpful to expose the chosen trim mode to userland. Create a
> sysfs "trim" attribute for each ata_device that displays whether trim is
> "unsupported", "unqueued" or "queued".
Thank you Martin, this is a really great idea following on from those
discussions on the btrfs list on how to work out whether a drive supports trim
and, if so, whether it's the original or new variant.
I'm hoping to have some time this weekend to test these patches out; should I
test them on 3.14 or the current master for 3.15, or both?
Much obliged!
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2014-04-04 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 0:42 [PATCH 1/2] libata: Expose trim capability in sysfs Martin K. Petersen
2014-04-02 0:42 ` [PATCH 2/2] libata: Update queued trim blacklist for M5x0 drives Martin K. Petersen
2014-04-02 17:11 ` Tejun Heo
2014-04-02 17:09 ` [PATCH 1/2] libata: Expose trim capability in sysfs Tejun Heo
2014-04-02 17:26 ` Martin K. Petersen
2014-04-04 17:29 ` Marc MERLIN
2014-04-04 21:49 ` Chris Samuel [this message]
2014-04-05 8:12 ` Chris Samuel
2014-04-07 19:52 ` Martin K. Petersen
2014-04-06 4:03 ` Marc MERLIN
[not found] ` <1403024.0HLhjfholh@quad>
2014-04-06 6:19 ` Marc MERLIN
2014-04-16 20:16 ` Tejun Heo
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=7474970.Ep9zfmpRio@quad \
--to=chris@csamuel.org \
--cc=linux-ide@vger.kernel.org \
--cc=marc@merlins.org \
--cc=martin.petersen@oracle.com \
--cc=tj@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).