From: Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>
To: "Steve French" <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Andrés Souto" <kai670-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: CIFS <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
samba-technical
<samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org>
Subject: Re: Fwd: [PATCH] cifs: add .splice_write
Date: Sat, 27 Jan 2018 07:31:32 -0700 [thread overview]
Message-ID: <f29bddaa-62b5-046d-70f9-b809fd41a1d7@kernel.dk> (raw)
In-Reply-To: <CAH2r5mvgTBdwBgsA4r0x7KiuLEzW2YeU4Hz+PUeYyvooMCSN4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 1/26/18 2:25 PM, Steve French wrote:
> The patch did look like it improves the performance of file copy from
> Nautilus when I tried it, but would prefer experimenting tool where I
> could measure the improvement more precisely. Is there a good command
> line tool which generates splice_write indirectly? As expected cp and
> dd don't seem to be affected by this patch.
You can use fio with ioengine=splice. Or if you have any sendfile()
based tools, that should also do the trick, as sendfile() is just
a wrapper around splice.
--
Jens Axboe
next prev parent reply other threads:[~2018-01-27 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 13:23 [PATCH] cifs: add .splice_write Andrés Souto
[not found] ` <20171228132308.5709-1-kai670-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-01-26 18:13 ` Andrés Souto
2018-01-26 21:25 ` Fwd: " Steve French
[not found] ` <CAH2r5mvgTBdwBgsA4r0x7KiuLEzW2YeU4Hz+PUeYyvooMCSN4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-27 14:31 ` Jens Axboe [this message]
2018-01-29 10:47 ` Andrés Souto
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=f29bddaa-62b5-046d-70f9-b809fd41a1d7@kernel.dk \
--to=axboe-tswwg44o7x1aa/9udqfwiw@public.gmane.org \
--cc=kai670-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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