public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Peter Niemayer <niemayer@isg.de>
Cc: xfs@oss.sgi.com
Subject: Re: XFS support for TRIM / blkdev_issue_discard?
Date: Fri, 17 Apr 2009 11:50:54 -0500	[thread overview]
Message-ID: <49E8B36E.1080508@sandeen.net> (raw)
In-Reply-To: <49E8A9C8.5030705@isg.de>

Peter Niemayer wrote:
> Update: In a recent forum entry
>   ( http://www.ocztechnologyforum.com/forum/showthread.php?t=54379&page=11 )
> Mark Lord (the maintainer of the "hdparm" tool) states that according
> to his tests the newly added support for discarding sectors works in
> the Linux "ext4" filesystem.
> (Support in GFS2 and swap filesystems has already been available before).
> 
> Isn't that another good reason enable XFS to do that, too? :-)

I don't think anyone disagrees that it's a good idea; it's a question of
resources and priorities, is all.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-04-17 16:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31  5:30 [GIT PULL] XFS update for 2.6.30 Felix Blyakher
2009-04-02 16:26 ` Felix Blyakher
2009-04-03 16:52   ` Linus Torvalds
2009-04-03 17:02     ` Linus Torvalds
2009-04-03 17:41       ` Felix Blyakher
2009-04-04  1:19         ` david
2009-04-04  1:54           ` Felix Blyakher
2009-04-14 14:44 ` XFS support for TRIM / blkdev_issue_discard? Peter Niemayer
2009-04-14 18:32   ` Felix Blyakher
2009-04-15  9:43     ` Peter Niemayer
2009-04-15 11:58     ` Peter Niemayer
2009-04-17 16:09     ` Peter Niemayer
2009-04-17 16:50       ` Eric Sandeen [this message]
2009-04-19  8:19     ` Dave Chinner
2009-04-19 15:51       ` Eric Sandeen
2009-04-20 18:45         ` Peter Niemayer
2009-04-20 19:11           ` Martin K. Petersen

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=49E8B36E.1080508@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=niemayer@isg.de \
    --cc=xfs@oss.sgi.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