From: Wallak <wallak@free.fr>
To: Rik van Riel <riel@redhat.com>
Cc: Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, jweiner@redhat.com
Subject: Re: File copy is very slow on linux-3.4.2 (or linux-3.3x) on a specific hardware: AMD FX-8150 + 990FX (solved?)
Date: Sat, 16 Jun 2012 21:32:41 +0200 [thread overview]
Message-ID: <4FDCDF59.9020208@free.fr> (raw)
In-Reply-To: <4FDA5048.5000107@redhat.com>
Rik van Riel wrote:
> On 06/13/2012 04:37 PM, Wallak wrote:
>
>> HighTotal: 8052692 kB HighTotal: 8052692 kB
>> HighFree: 7978664 kB | HighFree: 6227412 kB
>> LowTotal: 229508 kB LowTotal: 229508 kB
>> LowFree: 195804 kB | LowFree: 148948 kB
>
> Did the BIOS remap essentially all of the low memory
> to end up above the 1GB boundary?
May be not, but there was also a vmalloc= option on the linux
command line; Theses options must be used with caution, and takes some
low memory.
>
> This does not look like a system that should be run
> with a 32 bit kernel, since it only has 200MB of lowmem,
> giving you a 40:1 highmem:lowmem ratio, which is really
> too much to run well.
>
You are right; I will try also in 64-bits mode.
Wallak.
prev parent reply other threads:[~2012-06-16 19:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1108815600.134531433.1339443818361.JavaMail.root@zimbra44-e7.priv.proxad.net>
2012-06-11 19:54 ` File copy is very slow on linux-3.4.2 (or linux-3.3x) on a specific hardware: AMD FX-8150 + 990FX wallak
2012-06-11 20:48 ` Borislav Petkov
2012-06-11 23:19 ` Wallak
2012-06-12 16:53 ` Jan Kara
2012-06-12 18:39 ` Wallak
2012-06-12 21:09 ` Jan Kara
2012-06-12 22:41 ` Wallak
2012-06-13 6:53 ` Jan Kara
2012-06-13 20:37 ` File copy is very slow on linux-3.4.2 (or linux-3.3x) on a specific hardware: AMD FX-8150 + 990FX (solved?) Wallak
2012-06-13 22:38 ` Johannes Weiner
2012-06-14 20:16 ` Wallak
2012-06-14 20:57 ` Rik van Riel
2012-06-16 19:32 ` Wallak [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=4FDCDF59.9020208@free.fr \
--to=wallak@free.fr \
--cc=jack@suse.cz \
--cc=jweiner@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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