From: Joe Ceklosky <jfceklosky@gmail.com>
To: linux-mm@kvack.org
Subject: Possible 32-bit PAE kernel I/O slow down with 3.3.X
Date: Wed, 25 Apr 2012 23:22:56 -0400 [thread overview]
Message-ID: <4F98BF90.9050703@gmail.com> (raw)
I have notice significant slow downs with disk I/O on a 32-bit PAE 3.3.X
kernels.
The test machine has 16GB memory, Intel i5 CPU, Intel
motherboard, and an Intel 160GB SSD. I copied 536M from one partition
on an SSD to another.
Test 1:
kernel 3.3.2 32-bit PAE with kernel parm mem=3G
time cp -ra testdir/ /tmp
real 0m8.989s
user 0m0.094s
sys 0m1.080s
Test 2:
kernel 3.3.2 32-bit PAE
time cp -ra testdir/ /tmp
real 1m17.068s
user 0m0.173s
sys 0m2.149s
Also I tested kernel 3.2.16 32-bit PAE with no memory limits and it
was in line with test 1.
Am I doing something wrong or could something have been broken in PAE
with kernel 3.3.X?
Thanks,
Joe Ceklosky
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2012-04-26 3:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F98BF90.9050703@gmail.com \
--to=jfceklosky@gmail.com \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).