From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Namjae Jeon <namjae.jeon@samsung.com>,
Amit Sahrawat <a.sahrawat@samsung.com>
Subject: Re: [PATCH RESEND v5] fat: editions to support fat_fallocate
Date: Thu, 02 May 2013 18:34:08 +0900 [thread overview]
Message-ID: <87fvy53eun.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <CAKYAXd_DRLG3KzjXEQ_8vD5mFWE95gR+jj3-MYhC3QKgQOLTEA@mail.gmail.com> (Namjae Jeon's message of "Thu, 2 May 2013 18:15:21 +0900")
Namjae Jeon <linkinjeon@gmail.com> writes:
>>> AFAIK, preallocation != fallocate. ext*'s preallocation was there at
>>> before fallocation to optimize block allocation for user data blocks.
> yes, this is correct , preallocation!= fallocate, we just adopted only
> the "release part" from that approach
> Sorry, Would you mind to adopt this approach :) ?
I'm ok as start if it works.
But from this discussion, discard at last close(2) doesn't look like
working for your requirement. Since you want to discard at last close of
inode, so, rather, I guess you actually want to discard at last
dereference of inode.
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2013-05-02 9:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 0:08 [PATCH RESEND v5] fat: editions to support fat_fallocate Namjae Jeon
2013-04-29 14:31 ` OGAWA Hirofumi
2013-05-01 4:14 ` Namjae Jeon
2013-05-01 6:42 ` OGAWA Hirofumi
2013-05-02 4:46 ` Namjae Jeon
2013-05-02 5:12 ` OGAWA Hirofumi
2013-05-02 6:12 ` Namjae Jeon
2013-05-02 7:36 ` OGAWA Hirofumi
2013-05-02 7:43 ` OGAWA Hirofumi
2013-05-02 9:15 ` Namjae Jeon
2013-05-02 9:34 ` OGAWA Hirofumi [this message]
2013-05-02 9:56 ` Namjae Jeon
2013-06-18 5:47 ` Namjae Jeon
2013-06-18 17:33 ` OGAWA Hirofumi
2013-06-20 6:28 ` Namjae Jeon
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=87fvy53eun.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=a.sahrawat@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.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).