linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Nikita@Namesys.COM, piggin@cyberone.com.au, linux-mm@kvack.org
Subject: Re: [PATCH 0/5] mm improvements
Date: Wed, 4 Feb 2004 13:04:40 -0800	[thread overview]
Message-ID: <20040204130440.71d4be3c.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0402042047040.4021-100000@localhost.localdomain>

Hugh Dickins <hugh@veritas.com> wrote:
>
> On Wed, 4 Feb 2004, Andrew Morton wrote:
> > Hugh Dickins <hugh@veritas.com> wrote:
> > >
> > >  Sorry, that BUG_ON is there for very good reason.  It's no disgrace
> > >  that your testing didn't notice the effect of passing a mapped page
> > >  down to shmem_writepage, but it is a serious breakage of tmpfs.
> > 
> > hm.  Can't I force writepage-of-a-mapped-page with msync()?
> 
> I hope not, __filemap_fdatawrite still starts off with:
> 
> 	if (mapping->backing_dev_info->memory_backed)
> 		return 0;

Sigh.  ->memory_backed is a crock.  It is excessively overloaded and needs
to be split up into several things which really mean something.

> Once upon a time you did have vmscan.c calling ->writepages, rather
> the effect that Nikita is trying for.  It was that writepages which
> led me to insert the BUG_ON and give tmpfs a dummy writepages.
> Later on you dropped the ->writepages from vmscan.c:
> do you remember why? would be useful info for Nikita.

I'd need to troll the changelogs to remember the exact reason.  I had the
standalone a_ops->vm_writeback thing in there, which was able to do
writearound against the targetted page.  iirc it was causing some difficulties and
as a big effort was underway to minimise the amount of writeout via vmscan
_anyway_, I decided to toss it all out, stick with page-at-a-time writepage.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

      reply	other threads:[~2004-02-04 21:04 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-04  9:39 Nick Piggin
2004-02-04  9:40 ` [PATCH 1/5] " Nick Piggin
2004-02-04 19:45   ` Rik van Riel
2004-02-09  7:00     ` Nick Piggin
2004-02-09 21:56       ` Rik van Riel
2004-02-04  9:40 ` [PATCH 2/5] " Nick Piggin
2004-02-04 10:10   ` Andrew Morton
2004-02-04 10:15     ` Nick Piggin
2004-02-04 15:27     ` Rik van Riel
2004-02-05  2:18       ` Nick Piggin
2004-02-04  9:41 ` [PATCH 3/5] " Nick Piggin
2004-02-04 15:28   ` Rik van Riel
2004-02-04 16:45     ` Nikita Danilov
2004-02-04 18:53       ` Andrew Morton
2004-02-05  2:10       ` Nick Piggin
2004-02-04  9:42 ` [PATCH 4/5] " Nick Piggin
2004-02-04 10:11   ` Andrew Morton
2004-02-04 10:19     ` Nick Piggin
2004-02-04  9:42 ` [PATCH 5/5] " Nick Piggin
2004-02-04 10:03   ` Nick Piggin
2004-02-04 10:18   ` Andrew Morton
2004-02-04 10:22     ` Nick Piggin
2004-02-04 13:25 ` [PATCH 0/5] " Nikita Danilov
2004-02-04 13:53   ` Hugh Dickins
2004-02-04 14:03     ` Nikita Danilov
2004-02-04 15:03       ` Hugh Dickins
2004-02-04 15:19         ` Nikita Danilov
2004-02-05  2:13           ` Nick Piggin
2004-02-05 14:03             ` Nikita Danilov
2004-02-05 15:11               ` Nick Piggin
2004-02-05 15:15                 ` Nick Piggin
2004-02-05 15:20                   ` Nikita Danilov
2004-02-05 15:33                     ` Nick Piggin
2004-02-05 15:46                       ` Nikita Danilov
2004-02-05 15:56                         ` Nick Piggin
2004-02-05 16:03                           ` Nikita Danilov
2004-02-05 16:09                             ` Nick Piggin
2004-02-04 18:33     ` Andrew Morton
2004-02-04 20:54       ` Hugh Dickins
2004-02-04 21:04         ` Andrew Morton [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=20040204130440.71d4be3c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Nikita@Namesys.COM \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=piggin@cyberone.com.au \
    /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