public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namjae Jeon <namjae.jeon@samsung.com>
To: 'Christoph Hellwig' <hch@infradead.org>
Cc: 'Luk?? Czerner' <lczerner@redhat.com>,
	'OGAWA Hirofumi' <hirofumi@mail.parknet.co.jp>,
	'Andrew Morton' <akpm@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org
Subject: RE: [PATCH v8 1/4] fat: add fat_fallocate operation
Date: Wed, 10 Dec 2014 21:10:08 +0900	[thread overview]
Message-ID: <003f01d01472$3d5089e0$b7f19da0$@samsung.com> (raw)
In-Reply-To: <20141210104524.GA865@infradead.org>

> 
> On Wed, Dec 10, 2014 at 07:42:16PM +0900, Namjae Jeon wrote:
> > User have to call fallocate again if opening file after close().
> > And fallocate() will skip allocation if fallocated blocks is avaiable.
> > Instead, It gurrantee to be available fallocated blocks between open
> > and close(). And I updated such limitation of fat fallocate in
> > Documentation.
> 
> Documentation doesn't help, this breaks application exposed semantics.
> 
> If you think there is a use case for non-persistant preallocations
> please propose a new fallocate flag for it, or given the lack of use
> case probably just add a fat specific ioctl instead.
Hi Christoph,
Yes, There are use cases from me and samba team also.
And it is fat's specific limitation. so looks better to add ioctl.

Thanks.


      reply	other threads:[~2014-12-10 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09  7:17 [PATCH v8 1/4] fat: add fat_fallocate operation Namjae Jeon
2014-12-09 14:21 ` Lukáš Czerner
2014-12-10 10:42   ` Namjae Jeon
2014-12-10 10:45     ` Christoph Hellwig
2014-12-10 12:10       ` 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='003f01d01472$3d5089e0$b7f19da0$@samsung.com' \
    --to=namjae.jeon@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=lczerner@redhat.com \
    --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