From: Andrey Savochkin <saw@saw.sw.com.sg>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Q about pagecache data never written to disk
Date: Mon, 6 Sep 2004 11:06:28 +0400 [thread overview]
Message-ID: <20040906110628.A31962@castle.nmd.msu.ru> (raw)
In-Reply-To: <20040905140040.58a5fcdc.akpm@osdl.org>; from "Andrew Morton" on Sun, Sep 05, 2004 at 02:00:40PM
On Sun, Sep 05, 2004 at 02:00:40PM -0700, Andrew Morton wrote:
> Andrey Savochkin <saw@saw.sw.com.sg> wrote:
> > On Sun, Sep 05, 2004 at 03:52:33AM -0700, Andrew Morton wrote:
> > > That would be a retrograde step - it would be nice to move in the other
> > > direction: perform disk allocation at writeback time rather than at write()
> > > time, even for regular write() data. To do that we (probably) need space
> > > reservation APIs. And yes, we perhaps could reserve space in the
> > > filesystem when that page is first written to.
> > >
> > > But then what would we do if there's no space? SIGBUS? SIGSEGV?
> > > Inappropriate. SIGENOSPC?
> >
> > Should the space be allocated on close()?
>
> What effect are you trying to achieve?
Sending a signal while there is still a process...
> > Who will get the signal if nobody accesses the file anymore?
>
> Nobody. That's the point. Plus there _is_ no signal defined for this.
> Neither in Linux nor in POSIX.
>
> > I'm also thinking about various shell scripts with redirects to files...
>
> ? I doubt that they're writing files via MAP_SHARED.
I was deliberating on your idea about delayed allocation for regular write()s
also...
next prev parent reply other threads:[~2004-09-06 7:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 8:01 Q about pagecache data never written to disk Andrey Savochkin
2004-09-05 9:22 ` William Lee Irwin III
2004-09-05 10:52 ` Andrew Morton
2004-09-05 11:43 ` Andrey Savochkin
2004-09-05 21:00 ` Andrew Morton
2004-09-06 7:06 ` Andrey Savochkin [this message]
2004-09-09 12:39 ` Pavel Machek
2004-09-09 13:15 ` Nick Piggin
2004-09-09 13:37 ` Pavel Machek
2004-09-09 13:32 ` Nick Piggin
2004-09-09 17:24 ` William Lee Irwin III
2004-09-09 17:14 ` Nick Piggin
2004-09-09 17:35 ` William Lee Irwin III
2004-09-05 16:33 ` William Lee Irwin III
2004-09-06 6:24 ` William Lee Irwin III
2004-09-06 7:02 ` Andrew Morton
2004-09-06 15:12 ` William Lee Irwin III
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=20040906110628.A31962@castle.nmd.msu.ru \
--to=saw@saw.sw.com.sg \
--cc=akpm@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.