public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Rik van Riel <riel@redhat.com>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, Robert_Hentosh@Dell.com,
	Con Kolivas <kernel@kolivas.org>
Subject: Re: [PATCH][1/2] adjust dirty threshold for lowmem-only mappings
Date: Sat, 25 Dec 2004 21:03:49 +0100	[thread overview]
Message-ID: <20041225200349.GA11116@dualathlon.random> (raw)
In-Reply-To: <20041225190710.GZ771@holomorphy.com>

On Sat, Dec 25, 2004 at 11:07:10AM -0800, William Lee Irwin III wrote:
> Lifting the artificial lowmem restrictions on blockdev mappings
> (thereby nuking mapping->gfp_mask altogether) would resolve a number of
> problems, not that anything making that much sense could ever happen.

I recall that such restriction is needed only for the buffercache, or
you'd need to change _all_ the fs to kmap before accessing metadata
(this is partly already happening for the dir in pagecache, but not for
everything else).

Whatever the problem is (assuming there's really a problem in the write
throttling) it isn't going away by eliminating that restriction. Just
think booting with mem=800M, it would run into the same issue that
happens right now with the artificial limitation and >=1G of ram.

2.4 has the same limitation and it has no problem with write throttling
(and from my part 2.6 is working fine too with the 4 patches I posted,
it's not me being able to reproduce it).

  reply	other threads:[~2004-12-25 20:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-20 15:15 [PATCH][1/2] adjust dirty threshold for lowmem-only mappings Rik van Riel
2004-12-20 15:23 ` Rik van Riel
2004-12-20 20:54 ` Andrew Morton
2004-12-20 21:27   ` Rik van Riel
2004-12-23 19:21   ` Rik van Riel
2004-12-24 16:01     ` Andrea Arcangeli
2004-12-24 16:22       ` Rik van Riel
2004-12-24 16:40         ` Andrea Arcangeli
2004-12-24 22:12           ` Rik van Riel
2004-12-25  2:07             ` Andrea Arcangeli
2004-12-25 17:59               ` Rik van Riel
2004-12-25 18:36                 ` Andrea Arcangeli
2004-12-25 19:07                 ` William Lee Irwin III
2004-12-25 20:03                   ` Andrea Arcangeli [this message]
2004-12-26  3:07                     ` William Lee Irwin III
2005-01-02 16:10                       ` Andrea Arcangeli
2005-01-02 16:36                         ` William Lee Irwin III
2005-01-02 16:53                         ` Rik van Riel
2005-01-02 17:21                           ` Andrea Arcangeli
2004-12-25 22:03                   ` Nikita Danilov
2004-12-26  3:16                     ` William Lee Irwin III
2005-01-02 15:11                   ` Jens Axboe
2005-01-02 16:18                     ` Andrea Arcangeli
2005-01-02 20:03                     ` Andrew Morton
2005-01-02 20:25                       ` William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
2004-12-20 16:46 Robert_Hentosh
2004-12-20 17:56 ` Sami Farin

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=20041225200349.GA11116@dualathlon.random \
    --to=andrea@suse.de \
    --cc=Robert_Hentosh@Dell.com \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=wli@holomorphy.com \
    /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