From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Pavel Emelyanov <xemul@parallels.com>
Subject: Re: [PATCH -next] fs: pipe -- Take into account requested @len in iter_file_splice_write
Date: Tue, 3 Jun 2014 14:19:28 +0400 [thread overview]
Message-ID: <20140603101928.GD17659@moon> (raw)
In-Reply-To: <20140530203332.GA23463@moon>
On Sat, May 31, 2014 at 12:33:32AM +0400, Cyrill Gorcunov wrote:
> Currently iter_file_splice_write pushes into the output IOVs as much
> as it can, so that if one previously pushed into pipe 8K of data and
> then try to fetch 4K -- he get the complete 8K instead.
>
> Lest count how many bytes were requested by a caller and
> stop looping once request is complete.
>
> Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>
Ping?
prev parent reply other threads:[~2014-06-03 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 20:33 [PATCH -next] fs: pipe -- Take into account requested @len in iter_file_splice_write Cyrill Gorcunov
2014-06-03 10:19 ` Cyrill Gorcunov [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=20140603101928.GD17659@moon \
--to=gorcunov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=xemul@parallels.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