public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Snook <csnook@redhat.com>
To: Eric Hopper <hopper@omnifarious.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nosync, an idea for general filesystem mount flag
Date: Wed, 07 Jan 2009 12:35:42 -0500	[thread overview]
Message-ID: <4964E7EE.7090301@redhat.com> (raw)
In-Reply-To: <20090106184205.GC15454@omnifarious.org>

Eric Hopper wrote:
> Maybe somebody has thought of this before.  But I think it would be
> useful to have a mount flag telling the filesystem layer that a certain
> filesystem never ever needs to be synced, even when the 'sync' system
> call is called.
> 
> My /tmp, for example, is reformatted on each and every boot.  There is
> no reason for anything written to /tmp to ever hit the disk.  The only
> reason is to make room for something else in memory.
> 
> I think this could potentially help out notebooks that only had solid
> state drives.
> 
> Anyway, just a random thought,

This is why tmpfs was written, but if you're using an SSD with large erase 
blocks, and want to avoid setting up a swap partition, you could put the 
filesystem on a loop device instead.  The sync calls would be absorbed as writes 
to the non-sync backing file.  It's slightly more complicated to set up, and 
slightly less flexible, but the next generation SSDs won't have problems with 
random write performance, so the convenience of implementing such an option 
would be rather short-lived.  It's not a fundamentally evil idea, but it just 
doesn't seem to be worth the effort, particularly to maintain it for the rest of 
eternity.

-- Chris

      reply	other threads:[~2009-01-07 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06 18:42 nosync, an idea for general filesystem mount flag Eric Hopper
2009-01-07 17:35 ` Chris Snook [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=4964E7EE.7090301@redhat.com \
    --to=csnook@redhat.com \
    --cc=hopper@omnifarious.org \
    --cc=linux-kernel@vger.kernel.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