public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Kyungmin Park <kmpark@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Lukas Czerner <lczerner@redhat.com>
Subject: Re: [PATCH v6] fat: Batched discard support for fat
Date: Tue, 29 Mar 2011 16:28:33 +0900	[thread overview]
Message-ID: <878vvy4c7y.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <AANLkTinMK8oXEJdYEqjRSfC348xnGx9Fmc8mRXOVN0AZ@mail.gmail.com> (Kyungmin Park's message of "Tue, 29 Mar 2011 15:42:03 +0900")

Kyungmin Park <kmpark@infradead.org> writes:

>> I looked at fstrim.c. It is lowlevel tools to just issue FITRIM - it
>> doesn't use the result at all.
>>
>> Um. Honestly I'd like to see more or wait until real user for now,
>> instead of providing unclear design.
>
> You can find the testcase xfs251(?)
>
> and it's our our usage. After UMS support finished, execute the trim
> command from 0 to MAXINT.
> and periodically call the trim FAT partitions.

It seems to be using fstrim. So state is same with fstrim.
More detail is,

1) This means to trim 0-ULLONG

   fstrim mntpoint

2) step for each 1GB

   while all blocks; do
       fstrim -s start -l step mntpoint
   done

Those bring the real problem up on this example. What is right behavior
if start + len is outside the end of FS? Also I think other issues on
this thread are same state.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2011-03-29  7:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 10:34 [PATCH v6] fat: Batched discard support for fat Kyungmin Park
2011-03-29  5:04 ` OGAWA Hirofumi
2011-03-29  5:11   ` Kyungmin Park
2011-03-29  6:37     ` OGAWA Hirofumi
2011-03-29  6:42       ` Kyungmin Park
2011-03-29  7:28         ` OGAWA Hirofumi [this message]
2011-03-30 13:22 ` Arnd Bergmann
2011-03-30 13:50   ` Lukas Czerner
2011-03-30 13:58     ` Kyungmin Park
2011-03-30 14:45       ` Arnd Bergmann
2011-03-30 14:20     ` Arnd Bergmann
2011-03-30 14:44       ` Kyungmin Park
2011-03-30 15:06         ` Arnd Bergmann
2011-05-24  1:18           ` Kyungmin Park
2011-05-24  4:47             ` OGAWA Hirofumi
2011-05-24  5:21               ` Kyungmin Park
2011-05-24  6:39                 ` OGAWA Hirofumi
2011-05-24  6:55                   ` Kyungmin Park
2011-05-24  7:32                     ` OGAWA Hirofumi
2011-05-24  8:54                       ` Kyungmin Park
2011-05-24  9:44                         ` OGAWA Hirofumi
2011-05-24  9:25                       ` Lukas Czerner
2011-05-24 10:07                         ` OGAWA Hirofumi
2011-05-24 10:44                           ` Lukas Czerner
2011-05-24 11:14                             ` OGAWA Hirofumi
2011-05-24 11:32                               ` Lukas Czerner
2011-05-24 12:19                                 ` OGAWA Hirofumi
2011-05-24 13:30                                   ` Lukas Czerner
2011-05-24 14:19                                     ` OGAWA Hirofumi
2011-08-31 13:02                                       ` Kyungmin Park
2011-08-31 17:51                                         ` OGAWA Hirofumi
2011-10-05 14:38                                           ` Lukas Czerner

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=878vvy4c7y.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=kmpark@infradead.org \
    --cc=lczerner@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox