From: "Kyungmin Park" <kmpark@infradead.org>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Dongjun Shin" <djshin90@gmail.com>, "Greg Banks" <gnb@sgi.com>,
"Linux Filesystem Mailing List" <linux-fsdevel@vger.kernel.org>,
"David Chinner" <dgc@melbourne.sgi.com>,
"Donald Douwsma" <donaldd@melbourne.sgi.com>,
"Christoph Hellwig" <hch@infradead.org>,
"Roger Strassburg" <rls@sgi.com>, "Mark Goodwin" <markgw@sgi.com>,
"Brett Jon Grandbois" <brettg@melbourne.sgi.com>
Subject: Re: Proposal to improve filesystem/block snapshot interaction
Date: Wed, 31 Oct 2007 08:42:11 +0900 [thread overview]
Message-ID: <9c9fda240710301642u79ccb6bar5f84cadf10086b0f@mail.gmail.com> (raw)
In-Reply-To: <200710301115.30376.arnd@arndb.de>
On 10/30/07, Arnd Bergmann <arnd@arndb.de> wrote:
> On Tuesday 30 October 2007, Dongjun Shin wrote:
> > There is an ongoing discussion about adding 'Trim' ATA command for notifying
> > the drive about the deleted blocks.
> >
> > http://www.t13.org/Documents/UploadedDocuments/docs2007/e07154r3-Data_Set_Management_Proposal_for_ATA-ACS2.pdf
> >
> > This is especially useful for the storage device like Solid State Drive (SSD).
> >
> This make me curious, why would t13 want to invent a new command when
> there is already the erase command from CFA?
>
> It's not exactly the same, but close enough that the proposed BIO_HINT_RELEASE
> should probably be mapped to CFA_ERASE (0xc0) on drives that support it:
> http://t13.org/Documents/UploadedDocuments/technical/d97116r1.pdf
>
IHMO, the main difference is that it requires the physical operation or not.
The CFA_ERAES erases the free blocks, it requires the physical erase operation.
But in trim case, it just unmapped the free blocks at FTL level. it
doesn't require the physical operation.
It's time saving and we can do a lot of works at FTL level internally.
Thank you,
Kyungmin Park
I
next prev parent reply other threads:[~2007-10-30 23:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070927063113.GD2989@sgi.com>
2007-10-30 1:04 ` Proposal to improve filesystem/block snapshot interaction Greg Banks
2007-10-30 1:11 ` Greg Banks
2007-10-30 4:16 ` Neil Brown
2007-10-30 5:12 ` Greg Banks
2007-10-30 7:43 ` Arnd Bergmann
2007-11-20 23:43 ` Roger Strassburg
2007-10-30 23:56 ` David Chinner
2007-10-31 4:01 ` Greg Banks
2007-10-31 7:04 ` David Chinner
2007-10-30 9:35 ` Dongjun Shin
2007-10-30 10:15 ` Arnd Bergmann
2007-10-30 10:49 ` Dongjun Shin
2007-10-30 12:38 ` Arnd Bergmann
2007-10-30 14:19 ` Dongjun Shin
2007-10-30 15:37 ` Jörn Engel
2007-10-30 16:37 ` Arnd Bergmann
2007-10-30 23:19 ` Kyungmin Park
2007-10-30 23:42 ` Kyungmin Park [this message]
2007-10-30 14:06 ` Jörn Engel
2007-10-31 3:44 ` Greg Banks
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=9c9fda240710301642u79ccb6bar5f84cadf10086b0f@mail.gmail.com \
--to=kmpark@infradead.org \
--cc=arnd@arndb.de \
--cc=brettg@melbourne.sgi.com \
--cc=dgc@melbourne.sgi.com \
--cc=djshin90@gmail.com \
--cc=donaldd@melbourne.sgi.com \
--cc=gnb@sgi.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=markgw@sgi.com \
--cc=rls@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;
as well as URLs for NNTP newsgroup(s).