From: Dmitry Monakhov <dmonakhov@openvz.org>
To: "linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-fsdevel\@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch] RFC directio: partial writes support
Date: Sat, 27 Feb 2010 14:10:35 +0300 [thread overview]
Message-ID: <87vddj6ij8.fsf@openvz.org> (raw)
In-Reply-To: <87iq9lxz3t.fsf@openvz.org> (Dmitry Monakhov's message of "Thu, 25 Feb 2010 15:45:58 +0300")
Dmitry Monakhov <dmonakhov@openvz.org> writes:
> Can someone please describe me why directio deny partial writes.
> For example if someone try to write 100Mb but file system has less
> data it return ENOSPC in the middle of block allocation.
> All allocated blocks will be truncated (it may be 100Mb -4k) end
> ENOSPC will be returned. As far as i remember direct_io always act
> like this, but i never asked why?
> Why do we have to give up all the progress we made?
> In fact partial writes are possible in case of holes, when we
> fall back to buffered write. XFS implemented partial writes.
>
> I've done trivial changes and it works like charm.
> Let's enable partial writes support and allow caller to define
> this behavior.
add Andrew to cc:
next prev parent reply other threads:[~2010-02-27 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 12:45 [patch] RFC directio: partial writes support Dmitry Monakhov
2010-02-27 11:10 ` Dmitry Monakhov [this message]
2010-03-01 23:21 ` Andrew Morton
2010-03-02 9:25 ` Nick Piggin
2010-03-02 11:34 ` Jan Kara
2010-03-02 12:37 ` Nick Piggin
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=87vddj6ij8.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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