From: Namjae Jeon <namjae.jeon@samsung.com>
To: 'OGAWA Hirofumi' <hirofumi@mail.parknet.co.jp>
Cc: 'Andrew Morton' <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org
Subject: RE: [PATCH v6 0/4] fat: additions to support fat_fallocate
Date: Fri, 24 Oct 2014 08:52:44 +0900 [thread overview]
Message-ID: <001c01cfef1c$70dda390$5298eab0$@samsung.com> (raw)
In-Reply-To: <87bnp294sn.fsf@devron.myhome.or.jp>
> Namjae Jeon <namjae.jeon@samsung.com> writes:
>
> > This patch set provides support for doing fallocate operation
> > on FAT filesystem.
>
> I'm still not reviewing deeply though, basically looks like good to
> me. But I'm still not testing this one at all, sorry.
>
> If not tested yet, we would be able to start test, e.g. stress.
Hi, OGAWA.
Okay, I will share stress test result(per sector size) using fsx, fsstress, etc.
And will fix the review points of 2/4, 3/4 patch also.
Thanks for review!
>
> Thanks.
>
> > v6:
> > - Remove usage of i_disksize
> > - Align all fallocate code sequence to use i_blocks as
> > this is more or less can be used to denote the on-disksize.
> > Also, i_blocks is common in update path of cluster allocation via.
> > fat_chain_add() both from normal write path and fallocate() operation
> >
> > v5:
> > - change all routines to make ->i_disksize aligned by cluster size.
> > - merge fat_bmap2() and fat_get_block_bmap().
> >
> > v4:
> > - ->i_disksize is aligned by block size in fill_inode.
> > - use i_disksize when computing the number of cluster for fallocate.
> > - make fat_get_block_bmap to avoid race issue.
> > - use __fat_write_inode() with inode_needs_sync() in evict.
> >
> > v3:
> > - fix i_disksize and mmu_private comments(uninit/initialized)
> > - remove unneeded condition in fat_bmap.
> > - use mmu_private instead of fclus in fat_fallocate.
> > - make function mark buffer new for block in fallocated region.
> > - use flags for bmap.
> > - use mmu_private instead of i_size in direct_IO.
> > - use flags and remove i_mutex in bmap.
> > - update vfat documentation.
> >
> > v2:
> > - remove a stary unlock(from Dan Carpenter)
> > - check ->mmu_private and ->i_disksize to truncate uninitialized data.
> >
> > Namjae Jeon (4):
> > fat: add fat_fallocate operation
> > fat: skip cluster allocation on fallocated region
> > fat: permit to return phy block number by fibmap in fallocated region
> > Documentation/filesystems/vfat.txt: update the limitation for fat
> > fallocate
>
> --
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2014-10-23 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 11:26 [PATCH v6 0/4] fat: additions to support fat_fallocate Namjae Jeon
2014-10-23 15:36 ` OGAWA Hirofumi
2014-10-23 23:52 ` Namjae Jeon [this message]
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='001c01cfef1c$70dda390$5298eab0$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).