From: Jens Axboe <axboe@suse.de>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Rik van Riel <riel@redhat.com>, Andrea Arcangeli <andrea@suse.de>,
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: Sun, 2 Jan 2005 16:11:47 +0100 [thread overview]
Message-ID: <20050102151147.GA1930@suse.de> (raw)
In-Reply-To: <20041225190710.GZ771@holomorphy.com>
On Sat, Dec 25 2004, William Lee Irwin III wrote:
> On Sat, 25 Dec 2004, Andrea Arcangeli wrote:
> >> the first place? If that happens it means you're under a lowmem
> >> shortage, something you apparently ruled out when you said
> >> lowmem_reserve couldn't help your workload.
>
> On Sat, Dec 25, 2004 at 12:59:10PM -0500, Rik van Riel wrote:
> > Let me explain a 3rd time:
> [...]
> > If you have any more questions as to why the bug happens, don't
> > hesitate to ask and I'll explain you why this problem happens.
>
> This is an old and well-known problem.
>
> 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.
It should be lifted for block devices, it doesn't make any sense.
mapping->gfp_mask is still needed for things like loop though, so it
cannot be nuked.
--
Jens Axboe
next prev parent reply other threads:[~2005-01-02 15:13 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
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 [this message]
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=20050102151147.GA1930@suse.de \
--to=axboe@suse.de \
--cc=Robert_Hentosh@Dell.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--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 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.