linux-kernel - Re: [RFC PATCH] fuse: support splice() reading from fuse device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <E1OFCFp-0000dB-Es@pomaz-ex.szeredi.hu>
Date:	Thu, 20 May 2010 22:22:05 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Matthew Wilcox <matthew@....cx>
CC:	miklos@...redi.hu, torvalds@...ux-foundation.org,
	linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, jens.axboe@...cle.com,
	akpm@...ux-foundation.org
Subject: Re: [RFC PATCH] fuse: support splice() reading from fuse device

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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/