[lkml]   [2008]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Is there a "blackhole" /dev/null directory?
Jasper Bryant-Greene <> writes:
> This could be done fairly trivially with FUSE, and IMHO is a good use
> for FUSE because since you're just throwing most data away, performance
> is not a concern.

Q.: how much work would fuse have to do until the user file system
server could decide to ignore the data?
A.: pretty much all of a cached write including all the copies and
context switches.

That is because FUSE has to first hand all the data to the server
until it can decide to do nothing and that's pretty much all (and then
some more) of the cost of a cached write.

So if you want any performance benefit from this (I'm a little sceptical) you
should exactly not use FUSE.

The basic problem with the idea is that programs who create temporary
files usually want to read them back at some point too. So if you
throw everything away things break.

If you just don't want the write to not (usually) hit disk you
can use tmpfs, although I believe at least ext2 (not ext3 unfortunately)
is also reasonably good at not writing out very short lived files.


 \ /
  Last update: 2008-02-14 10:49    [W:0.132 / U:4.852 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site