LKML Archive on
help / color / mirror / Atom feed
From: Andi Kleen <>
To: Jasper Bryant-Greene <>
Cc: rzryyvzy <>,
Subject: Re: Is there a "blackhole" /dev/null directory?
Date: Thu, 14 Feb 2008 10:46:11 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Jasper Bryant-Greene's message of "Thu\, 14 Feb 2008 22\:39\:17 +1300")

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.


  reply	other threads:[~2008-02-14  9:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14  9:30 rzryyvzy
2008-02-14  9:39 ` Jasper Bryant-Greene
2008-02-14  9:46   ` Andi Kleen [this message]
2008-02-14 15:00     ` Jan Engelhardt
2008-02-14 15:19       ` Hans-Jürgen Koch
2008-02-14 15:23         ` Jan Engelhardt
2008-02-14 15:30           ` Hans-Jürgen Koch
2008-02-15 19:25       ` Bill Davidsen
2008-02-14 12:16   ` Mika Lawando
2008-02-14 15:06     ` linux-os (Dick Johnson)
     [not found] <>
2008-02-14 17:16 ` Bodo Eggert
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <>
     [not found]       ` <>
2008-02-15  1:15         ` Bodo Eggert

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \
    --subject='Re: Is there a "blackhole" /dev/null directory?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).