From: Linus Torvalds <torvalds@linux-foundation.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, jens.axboe@oracle.com,
akpm@linux-foundation.org
Subject: Re: [RFC PATCH] fuse: support splice() reading from fuse device
Date: Thu, 20 May 2010 12:19:08 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1005201215120.23538@i5.linux-foundation.org> (raw)
In-Reply-To: <E1OFAsd-0000Ra-1V@pomaz-ex.szeredi.hu>
On Thu, 20 May 2010, Miklos Szeredi wrote:
>
> So it's not the 20GB/s throughput that's interesting but the reduced
> CPU overhead, especially on slower processors. Apart from cache
> effects 20GB/s throughput with a null filesystem means 1% CPU at
> 200MB/s transfer speed with _any_ filesystem.
No it doesn't. Really.
It means 1% CPU at 200MB _IF_ you trigger the zero copy and nothing else!
But that's a damn big if. Does it ever trigger in practice? I doubt it. In
practice, you'll have to fill the pages with something in the first place.
In practice, the destination of the data is such that you'll often end up
copying anyway - it won't be /dev/null.
That's why I claim your benchmark is meaningless. It does NOT even say
what you claim it says. It does not say 1% CPU on a 200MB/s transfer,
exactly the same way my stupid pipe zero-copy didn't mean that people
could magically get MB/s throughput with 1% CPU on pipes.
It says nothing at all, in short. You need to have a real source, and a
real destination. Not some empty filesystem and /dev/null destination.
Linus
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-05-20 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 11:17 Miklos Szeredi
2010-05-20 11:28 ` Jens Axboe
2010-05-20 11:44 ` Miklos Szeredi
2010-05-20 17:49 ` Linus Torvalds
2010-05-20 17:58 ` Jens Axboe
2010-05-20 18:54 ` Miklos Szeredi
2010-05-20 19:19 ` Linus Torvalds [this message]
2010-05-20 20:07 ` Miklos Szeredi
2010-05-20 20:11 ` Matthew Wilcox
2010-05-20 20:22 ` Miklos Szeredi
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=alpine.LFD.2.00.1005201215120.23538@i5.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miklos@szeredi.hu \
/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