From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Tino Reichardt <list-linux-fsdevel@mcmilk.de>
Cc: jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [Jfs-discussion] [PATCH] fs/jfs: TRIM support for JFS Filesystem
Date: Wed, 01 Aug 2012 15:07:31 -0500 [thread overview]
Message-ID: <50198C83.4000500@oracle.com> (raw)
In-Reply-To: <20120801192934.GB19139@mcmilk.de>
On 08/01/2012 02:29 PM, Tino Reichardt wrote:
> * Dave Kleikamp <dave.kleikamp@oracle.com> wrote:
>> On 07/28/2012 06:08 AM, Tino Reichardt wrote:
>>> + tt->nblocks = 0; /* mark the current end */
>>> + for (tt = totrim; tt->nblocks != 0; tt++) {
>>> + if (!(JFS_SBI(sb)->flag & JFS_DISCARD)) {
>>> + /* not needed, when online discard is used */
>>
>> Why enter the function at all if JFS_DISCARD is set? But is this really
>> true? Removing files or file fragments that are smaller than
>> minblks_trim will fail to discard them dynamically.
>
> The other FS can also trim via fstrim(8) when mounted with discard
> option :) It is important, that a user can discard all free blocks, even
> when mounting with discard option. The FS could also be mounted several
> times without discard option, and then there are some ranges, where the
> device isn't informed about these ranges. So the batched discard ioctl()
> is then the only way to change that.
>
>
> The comment there was also a bit updated, here is it:
>
> /* when mounted with online discard, dbFree() will
> * call jfs_issue_discard() itself */
Ah. This comments makes it clear. I was forgetting that dbFree will
handle this.
Thanks,
Dave
next prev parent reply other threads:[~2012-08-01 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 21:32 [PATCH] fs/jfs: TRIM support for JFS Filesystem Tino Reichardt
2012-07-28 11:08 ` Tino Reichardt
2012-07-31 22:15 ` Dave Kleikamp
2012-07-31 22:15 ` [Jfs-discussion] " Dave Kleikamp
2012-08-01 19:29 ` Tino Reichardt
2012-08-01 20:07 ` Dave Kleikamp [this message]
2012-08-01 20:08 ` Tino Reichardt
2012-08-06 16:59 ` Tino Reichardt
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=50198C83.4000500@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=list-linux-fsdevel@mcmilk.de \
/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.