From: Satish Eerpini <eerpini@gmail.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Rik van Riel <riel@redhat.com>, Ray Lee <ray-lk@madrabbit.org>,
Christoph Lameter <cl@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: unresponsiveness on linux desktop during file copy
Date: Sun, 17 May 2009 06:57:03 +0530 [thread overview]
Message-ID: <93655eb70905161827x34a432ebn4910ee86d9bae30@mail.gmail.com> (raw)
In-Reply-To: <20090517011906.GA6375@localhost>
> Yes, better to apply Rik and mine patches together to get the best
> cache behavior. Rik's patch is crucial. They are both small patches,
> so can be backported trivially. Satish, what's your kernel version
> (or, do you want to try a newer kernel)? And the content of
> /proc/meminfo?
I am running 2.6.29.1 right now , just tell me which kernel to try, or
to which kernel I have to apply the patches and try them, I will test
the patches and let you know if the situation improves.
and the contents of /proc/meminfo are :
MemTotal: 2585724 kB
MemFree: 900524 kB
Buffers: 197504 kB
Cached: 1080332 kB
SwapCached: 0 kB
Active: 639544 kB
Inactive: 933068 kB
Active(anon): 307100 kB
Inactive(anon): 0 kB
Active(file): 332444 kB
Inactive(file): 933068 kB
Unevictable: 16 kB
Mlocked: 16 kB
HighTotal: 1707848 kB
HighFree: 321868 kB
LowTotal: 877876 kB
LowFree: 578656 kB
SwapTotal: 3526256 kB
SwapFree: 3526256 kB
Dirty: 1000 kB
Writeback: 0 kB
AnonPages: 294788 kB
Mapped: 80084 kB
Slab: 89692 kB
SReclaimable: 71436 kB
SUnreclaim: 18256 kB
PageTables: 6008 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 4819116 kB
Committed_AS: 796332 kB
VmallocTotal: 122880 kB
VmallocUsed: 8240 kB
VmallocChunk: 96952 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 4096 kB
DirectMap4k: 20472 kB
DirectMap4M: 884736 kB
Cheers
Satish
--
http://satish.playdrupal.com
next prev parent reply other threads:[~2009-05-17 1:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 17:07 Satish Eerpini
2009-05-15 17:12 ` Mark Knecht
[not found] ` <93655eb70905151024o634f8432j6c3db85df1f6ddfc@mail.gmail.com>
[not found] ` <5bdc1c8b0905151120p5aa58318t1765544fbbb695b2@mail.gmail.com>
2009-05-16 2:38 ` Satish Eerpini
2009-05-16 2:47 ` Mark Knecht
2009-05-16 3:12 ` Satish Eerpini
2009-05-16 3:37 ` Mark Knecht
2009-05-16 6:52 ` Satish Eerpini
2009-05-16 21:11 ` Mark Knecht
2009-05-17 8:54 ` Robert Hancock
2009-05-17 9:04 ` Satish Eerpini
2009-05-17 8:52 ` Robert Hancock
2009-05-15 18:02 ` Ray Lee
2009-05-15 19:33 ` Christoph Lameter
2009-05-16 16:03 ` Ray Lee
2009-05-16 17:38 ` Rik van Riel
2009-05-17 1:19 ` Wu Fengguang
2009-05-17 1:27 ` Satish Eerpini [this message]
2009-05-17 2:08 ` Wu Fengguang
2009-05-17 4:30 ` Satish Eerpini
2009-05-17 4:57 ` Arjan van de Ven
2009-05-17 4:58 ` Wu Fengguang
2009-05-17 6:18 ` Satish Eerpini
2009-05-17 9:30 ` Wu Fengguang
2009-05-17 12:01 ` Satish Eerpini
2009-05-17 12:17 ` Wu Fengguang
2009-05-17 12:27 ` Satish Eerpini
2009-05-17 12:39 ` Wu Fengguang
2009-05-17 13:03 ` Satish Eerpini
2009-05-17 13:11 ` Wu Fengguang
2009-05-17 13:43 ` Satish Eerpini
2009-05-17 13:14 ` Michael S. Zick
2009-05-16 2:28 ` Satish Eerpini
2009-05-16 14:25 ` Satish Eerpini
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=93655eb70905161827x34a432ebn4910ee86d9bae30@mail.gmail.com \
--to=eerpini@gmail.com \
--cc=cl@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.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
all inboxes | Powered by JetHome®