From: Cong Wang <amwang@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Pekka Enberg <penberg@kernel.org>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Lennart Poettering <lennart@poettering.net>,
Kay Sievers <kay.sievers@vrfy.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org
Subject: Re: [V2 PATCH] tmpfs: add fallocate support
Date: Tue, 22 Nov 2011 13:39:19 +0800 [thread overview]
Message-ID: <4ECB3587.3020909@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.00.1111201300340.1264@sister.anvils>
ao? 2011a1'11ae??21ae?JPY 05:22, Hugh Dickins a??e??:
> On Fri, 18 Nov 2011, Cong Wang wrote:
>
>> It seems that systemd needs tmpfs to support fallocate,
>> see http://lkml.org/lkml/2011/10/20/275. This patch adds
>> fallocate support to tmpfs.
>>
>> As we already have shmem_truncate_range(), it is also easy
>> to add FALLOC_FL_PUNCH_HOLE support too.
>
> Thank you, this version looks much much nicer.
>
> I wouldn't call it bug-free (don't you need a page_cache_release
> after the unlock_page?), and I won't be reviewing it and testing it
> for a week or two - there's a lot about the semantics of fallocate
> and punch-hole that's not obvious, and I'll have to study the mail
> threads discussing them before checking your patch.
Yeah, sorry, I missed unlock_page()...
>
> First question that springs to mind (to which I shall easily find
> an answer): is it actually acceptable for fallocate() to return
> -ENOSPC when it has already completed a part of the work?
Ah, good point, I will fix this as what Christoph suggested.
>
> But so long as the details don't end up complicating this
> significantly, since we anyway want to regularize the punch-hole
> situation by giving tmpfs the same interface to it as other filesystems,
> I now think it would be a bit perverse to disallow the original
> fallocate functionality that you implement here in-kernel.
>
Ok, I think you mean you are fine to accept it now?
Anyway, thanks a lot for your comments!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Cong Wang <amwang@redhat.com>
To: Hugh Dickins <hughd@google.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Pekka Enberg <penberg@kernel.org>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Lennart Poettering <lennart@poettering.net>,
Kay Sievers <kay.sievers@vrfy.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org
Subject: Re: [V2 PATCH] tmpfs: add fallocate support
Date: Tue, 22 Nov 2011 13:39:19 +0800 [thread overview]
Message-ID: <4ECB3587.3020909@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.00.1111201300340.1264@sister.anvils>
于 2011年11月21日 05:22, Hugh Dickins 写道:
> On Fri, 18 Nov 2011, Cong Wang wrote:
>
>> It seems that systemd needs tmpfs to support fallocate,
>> see http://lkml.org/lkml/2011/10/20/275. This patch adds
>> fallocate support to tmpfs.
>>
>> As we already have shmem_truncate_range(), it is also easy
>> to add FALLOC_FL_PUNCH_HOLE support too.
>
> Thank you, this version looks much much nicer.
>
> I wouldn't call it bug-free (don't you need a page_cache_release
> after the unlock_page?), and I won't be reviewing it and testing it
> for a week or two - there's a lot about the semantics of fallocate
> and punch-hole that's not obvious, and I'll have to study the mail
> threads discussing them before checking your patch.
Yeah, sorry, I missed unlock_page()...
>
> First question that springs to mind (to which I shall easily find
> an answer): is it actually acceptable for fallocate() to return
> -ENOSPC when it has already completed a part of the work?
Ah, good point, I will fix this as what Christoph suggested.
>
> But so long as the details don't end up complicating this
> significantly, since we anyway want to regularize the punch-hole
> situation by giving tmpfs the same interface to it as other filesystems,
> I now think it would be a bit perverse to disallow the original
> fallocate functionality that you implement here in-kernel.
>
Ok, I think you mean you are fine to accept it now?
Anyway, thanks a lot for your comments!
next prev parent reply other threads:[~2011-11-22 5:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 10:39 [V2 PATCH] tmpfs: add fallocate support Cong Wang
2011-11-18 10:39 ` Cong Wang
2011-11-19 10:03 ` Christoph Hellwig
2011-11-19 10:03 ` Christoph Hellwig
2011-11-19 14:14 ` Kay Sievers
2011-11-19 14:14 ` Kay Sievers
2011-11-20 21:39 ` Hugh Dickins
2011-11-21 10:11 ` Christoph Hellwig
2011-11-21 10:11 ` Christoph Hellwig
2011-11-21 22:13 ` Hugh Dickins
2011-11-21 22:13 ` Hugh Dickins
2011-11-22 5:50 ` Cong Wang
2011-11-22 5:50 ` Cong Wang
2011-11-21 10:06 ` Christoph Hellwig
2011-11-21 10:06 ` Christoph Hellwig
2011-11-22 5:39 ` Cong Wang
2011-11-22 5:39 ` Cong Wang
2011-11-20 21:22 ` Hugh Dickins
2011-11-20 21:22 ` Hugh Dickins
2011-11-21 10:11 ` Christoph Hellwig
2011-11-21 10:11 ` Christoph Hellwig
2011-11-22 5:39 ` Cong Wang [this message]
2011-11-22 5:39 ` Cong Wang
2011-11-22 22:06 ` Andrew Morton
2011-11-22 22:06 ` Andrew Morton
2011-11-23 4:30 ` Cong Wang
2011-11-23 4:30 ` Cong Wang
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=4ECB3587.3020909@redhat.com \
--to=amwang@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=kay.sievers@vrfy.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@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 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.