From: Andrew Morton <akpm@osdl.org>
To: Jens Axboe <axboe@suse.de>
Cc: eric@cisu.net, kernel@kolivas.org, barryn@pobox.com,
swsnyder@insightbb.com, linux-kernel@vger.kernel.org
Subject: Re: HIGHMEM4G config for 1GB RAM on desktop?
Date: Wed, 4 Aug 2004 12:06:33 -0700 [thread overview]
Message-ID: <20040804120633.4dca57b3.akpm@osdl.org> (raw)
In-Reply-To: <20040804130707.GN10340@suse.de>
Jens Axboe <axboe@suse.de> wrote:
>
> > > > -#define __PAGE_OFFSET (0xC0000000)
> > > > +#define __PAGE_OFFSET (0xB0000000)
> > > > #else
> > > > -#define __PAGE_OFFSET (0xC0000000UL)
> > > > +#define __PAGE_OFFSET (0xB0000000UL)
> > > > #endif
> > >
> > > Yup precisely. I agree that there probably isn't a whole lot of
> > > performance hit on a 1GB, it just seems silly that we need highmem on
> > > such a standard memory configuration these days. Especially when just
> > > moving the offset slightly removes that need.
> >
> > As a desktop user with 1024MB ram I agree that HIMEM has a silly threshold and
> > should not need to be enabled in this case. Its becoming common, especially
> > with dual channel memory systems to use 2x512MB sticks. On a hunch I bet
> > 2x512 is more common that 1x512 and 1x256 so why not merge this up? Who would
> > we submit this patch to?
>
> One way would be to ask Andrew what he thinks?
The 896M/128M split has a bit of a problem now each zone has its own LRU:
the size of the highmem zone is less than the amount of memory which is
described by the default /proc/sys/vm/dirty_ratio. So it is easy to
completely fill highmem with dirty pages. This causes a fairly large
amount of writeback via vmscan.c's writepage(). This causes poor I/O
submission patterns. This causes a simple large, linear `dd' write to run
at only 50-70% of disk bandwidth. (This was 6-12 months ago - it might be
a bit better now)
But I seem to be the only person who has noticed this yet ;) A workaround
is to decrease dirty_ratio and dirty_background_ratio.
Decreasing PAGE_OFFSET as above is attractive, but I believe 0xc0000000 is
part of the ABI, and although we know (from the 4g/4g and other such
patches) that everything will work OK, I wonder if it's really worth doing,
especially as it's a compile-time thing.
But hey, if someone can identify specific benefits from it then perhaps
sneaking in a config option, or maintaining an external patch would be
worthwhile.
next prev parent reply other threads:[~2004-08-04 19:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 21:02 HIGHMEM4G config for 1GB RAM on desktop? Steve Snyder
2004-08-02 21:32 ` Bart Alewijnse
2004-08-02 22:05 ` Barry K. Nathan
2004-08-03 13:30 ` Jens Axboe
2004-08-03 14:13 ` Prakash K. Cheemplavam
2004-08-03 14:29 ` Con Kolivas
2004-08-04 6:06 ` Jens Axboe
2004-08-04 11:14 ` Eric Bambach
2004-08-04 13:07 ` Jens Axboe
2004-08-04 19:06 ` Andrew Morton [this message]
2004-08-04 19:21 ` Marc-Christian Petersen
2004-08-04 19:30 ` Martin J. Bligh
2004-08-04 19:51 ` Andrew Morton
2004-08-04 20:09 ` Martin J. Bligh
2004-08-04 20:09 ` Roland Dreier
2004-08-04 20:13 ` Martin J. Bligh
2004-08-12 0:53 ` Timothy Miller
2004-08-30 18:06 ` Timothy Miller
2004-08-30 17:49 ` Miquel van Smoorenburg
2004-08-31 22:46 ` Timothy Miller
2004-09-01 7:52 ` Miquel van Smoorenburg
2004-09-01 9:38 ` Matt Heler
[not found] ` <1094030083l.3189l.2l@traveler>
[not found] ` <1094030194l.3189l.3l@traveler>
[not found] ` <200409010233.31643.lkml@lpbproductions.com>
2004-09-01 9:58 ` 3ware queue depth [was: Re: HIGHMEM4G config for 1GB RAM on desktop?] Miquel van Smoorenburg
2004-09-01 10:09 ` Christoph Hellwig
2004-09-01 11:08 ` Miquel van Smoorenburg
2004-09-01 11:43 ` Christoph Hellwig
2004-09-01 19:43 ` Patrick Mansfield
2004-09-01 22:23 ` Miquel van Smoorenburg
2004-09-04 10:10 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2004-08-06 12:52 HIGHMEM4G config for 1GB RAM on desktop? linux
2004-08-07 0:20 ` Valdis.Kletnieks
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=20040804120633.4dca57b3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=barryn@pobox.com \
--cc=eric@cisu.net \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swsnyder@insightbb.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.