From: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
To: Gordan Bobic <gordan-UpbECiGlrmGsTnJN9+BGXg@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: TRIM Support?
Date: Wed, 26 May 2010 10:40:52 +0900 [thread overview]
Message-ID: <87ljb7bftn.wl%jir@sekiba.com> (raw)
In-Reply-To: <4BFC1412.6000908-UpbECiGlrmGsTnJN9+BGXg@public.gmane.org>
hi
At Tue, 25 May 2010 19:16:50 +0100,
Gordan Bobic wrote:
>
> Hi,
>
> I notice that the pitch for NILFS is that it is particularly suitable
> for flash based media. Does it have any sort of support for TRIM
> command? If not, is there at least an equivalent of dumpfs that could be
> used to get the list of free blocks that could be passed to hdparm to
> issue TRIM commands to the SSD?
You may want to specify discard mount option for the purpose.
see Documentation/filesystems/nilfs2.txt
And if you want to see the usage of blocks, you can use combination of
lssu and dumpseg to see which block numbers are in use.
thanks,
regards,
> TIA.
>
> Gordan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
--
Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-05-26 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 18:16 TRIM Support? Gordan Bobic
[not found] ` <4BFC1412.6000908-UpbECiGlrmGsTnJN9+BGXg@public.gmane.org>
2010-05-26 1:40 ` Jiro SEKIBA [this message]
[not found] ` <87ljb7bftn.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-05-26 1:51 ` Ryusuke Konishi
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=87ljb7bftn.wl%jir@sekiba.com \
--to=jir-hfpbi5wx9j54eiagz67ipq@public.gmane.org \
--cc=gordan-UpbECiGlrmGsTnJN9+BGXg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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