From: Marc MERLIN <marc@merlins.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org, Chris Samuel <chris@csamuel.org>
Subject: Re: [PATCH 1/2] libata: Expose trim capability in sysfs
Date: Fri, 4 Apr 2014 10:29:11 -0700 [thread overview]
Message-ID: <20140404172911.GR19277@merlins.org> (raw)
In-Reply-To: <yq1zjk3wslj.fsf@sermon.lab.mkp.net>
On Wed, Apr 02, 2014 at 01:26:16PM -0400, Martin K. Petersen wrote:
> >>>>> "Tejun" == Tejun Heo <tj@kernel.org> writes:
>
> >> 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
>
> Tejun> Can you please be a bit more elaborate with how it'd be helpful?
> Tejun> Do we have actual use cases for it?
>
> There have been several threads on linux-btrfs and elsewhere where
> people have asked whether queued trim is supported by their drive or
> not. This information currently isn't reported anywhere. I thought it
> would be convenient to have a sysfs attribute that people could inspect
> to find out.
Hi Tejun,
I haven't had time to pull a new kernel and install the patches I need and
this one yet (sorry), but I wanted to give a +1 to that.
If queued trim is not available, people may want to disable trim if they
want fast performance for rm.
But indeed currently it's pretty hard to know if your drive supports it.
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2014-04-04 17:29 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 [this message]
2014-04-04 21:49 ` Chris Samuel
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=20140404172911.GR19277@merlins.org \
--to=marc@merlins.org \
--cc=chris@csamuel.org \
--cc=linux-ide@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.