From: Miklos Szeredi <miklos@szeredi.hu>
To: Matthew Wilcox <matthew@wil.cx>
Cc: miklos@szeredi.hu, torvalds@linux-foundation.org,
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 22:22:05 +0200 [thread overview]
Message-ID: <E1OFCFp-0000dB-Es@pomaz-ex.szeredi.hu> (raw)
In-Reply-To: <20100520201122.GL10452@parisc-linux.org> (message from Matthew Wilcox on Thu, 20 May 2010 14:11:22 -0600)
On Thu, 20 May 2010, Matthew Wilcox wrote:
> On Thu, May 20, 2010 at 10:07:23PM +0200, Miklos Szeredi wrote:
> > > 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.
> >
> > Sure, I will do that. It's just a lot harder to measure the effects
> > on hardware I have access to, where the CPU speed is just damn too
> > large compared to I/O speed.
>
> Try running a CPU burner on all the cores. Something that's low priority,
> so it'll be preempted by FUSE, and doesn't consume much cache.
Umm, that doesn't really make the CPU any slower, it just makes it
consume more power.
Miklos
--
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>
prev parent reply other threads:[~2010-05-20 20: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
2010-05-20 20:07 ` Miklos Szeredi
2010-05-20 20:11 ` Matthew Wilcox
2010-05-20 20:22 ` Miklos Szeredi [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=E1OFCFp-0000dB-Es@pomaz-ex.szeredi.hu \
--to=miklos@szeredi.hu \
--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=matthew@wil.cx \
--cc=torvalds@linux-foundation.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