From: Mauro Santos <registo.mailling@gmail.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Micky Ching <micky_ching@realsil.com.cn>,
Wei WANG <wei_wang@realsil.com.cn>,
linux-mmc <linux-mmc@vger.kernel.org>,
Roger Tseng <rogerable@realtek.com>,
Baolin Wang <baolin.wang@linaro.org>
Subject: Re: [PATCH 0/2] mmc: rtsx_pci: Enable support for erase/discard/trim requests
Date: Thu, 28 Jul 2016 00:07:39 +0100 [thread overview]
Message-ID: <49a04ef7-63c7-80c9-b64b-dcec18ecf815@gmail.com> (raw)
In-Reply-To: <CAPDyKFrYrGCEKqheL=C8gRczCO2TPhCMHKayD0xm47WJ2OA=fQ@mail.gmail.com>
On 27-07-2016 23:02, Ulf Hansson wrote:
> On 27 July 2016 at 22:35, Mauro Santos <registo.mailling@gmail.com> wrote:
>> On 27-07-2016 13:45, Ulf Hansson wrote:
>>> Mauro, I have applied this for my next branch (based on 4.7), to allow
>>> it to be easily tested.
>>>
>>> Just clone my tree below and build/replace your kernel.
>>> git://git.linaro.org/people/ulf.hansson/mmc.git next
>>>
>>> Running fstrim and checking blkdiscard should be sufficient as test cases.
>>>
>>> Don't hesitate to ask if problems occurs!
>>>
>>> Kind regards
>>> Uffe
>>>
>>
>> I've tested both blkdiscard and fstrim (on ext4) and they both worked.
>>
>> I haven't noticed any errors or warnings on dmesg or complaints from
>> blkdiscard/fstrim.
>>
>> If there are any more specific tests you would like me to do let me know.
>
> Perhaps just run some dd operation to read and write some data to the
> card, then I am happy. :)
>
Maybe I should have mentioned in my previous email, I have used the ext4
formatted fs to write some files, if you want me to still test with dd
let me know.
I have tested it like this:
- Filesystem was not mounted with the discard option.
- Almost fill the card with files, determine md5sum for all files and
reboot to make sure there are no cached files in ram
- Delete half of the files, fstrim -v (trimmed space looks about right),
check md5sum of remaining files - no problems here.
- fsck -f filesystem - no problems detected.
After this I have written more data to the card and checked the md5sums,
but I already forgot the exact sequence, I was looking for any sign that
using fstrim would delete more than it should have or that writing new
files might for some reason corrupt the old files.
I have confirmed that blkdiscard does work, the card returns zeros for
the few sectors I've checked, but I haven't confirmed that fstrim is
doing what it is supposed to do, the same applies to the case where the
filesystem is mounted with the discard option (quick google search
didn't return recipe for going from file->lba/sector or inode->lba/sector).
That said, given that blkdiscard works I'm assuming fstrim (and the
discard option) also work. I can check that if you want, but I would
need some pointers on how to do it. I could also check fstrim on a well
used f2fs formatted card where data should be all over the place by now.
> Thanks a lot for your help in testing, I will apply a tested-by tag
> from you, unless you object.
>
No objections.
> Kind regards
> Uffe
>
Regards,
Mauro Santos
next prev parent reply other threads:[~2016-07-27 23:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 12:25 [PATCH 0/2] mmc: rtsx_pci: Enable support for erase/discard/trim requests Ulf Hansson
2016-07-27 12:25 ` [PATCH 1/2] mmc: rtsx_pci: Use the provided busy timeout from the mmc core Ulf Hansson
2016-07-27 12:25 ` [PATCH 2/2] mmc: rtsx_pci: Enable MMC_CAP_ERASE to allow erase/discard/trim requests Ulf Hansson
2016-07-27 12:45 ` [PATCH 0/2] mmc: rtsx_pci: Enable support for " Ulf Hansson
2016-07-27 20:35 ` Mauro Santos
2016-07-27 22:02 ` Ulf Hansson
2016-07-27 23:07 ` Mauro Santos [this message]
2016-07-29 9:33 ` Ulf Hansson
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=49a04ef7-63c7-80c9-b64b-dcec18ecf815@gmail.com \
--to=registo.mailling@gmail.com \
--cc=baolin.wang@linaro.org \
--cc=linux-mmc@vger.kernel.org \
--cc=micky_ching@realsil.com.cn \
--cc=rogerable@realtek.com \
--cc=ulf.hansson@linaro.org \
--cc=wei_wang@realsil.com.cn \
/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