From: Wu Fengguang <fengguang.wu@intel.com>
To: Rik van Riel <riel@redhat.com>
Cc: Ray Lee <ray-lk@madrabbit.org>,
Christoph Lameter <cl@linux-foundation.org>,
Satish Eerpini <eerpini@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: unresponsiveness on linux desktop during file copy
Date: Sun, 17 May 2009 09:19:06 +0800 [thread overview]
Message-ID: <20090517011906.GA6375@localhost> (raw)
In-Reply-To: <4A0EFA08.4060106@redhat.com>
On Sun, May 17, 2009 at 01:38:16AM +0800, Rik van Riel wrote:
> Ray Lee wrote:
> > On Fri, May 15, 2009 at 12:33 PM, Christoph Lameter
> > <cl@linux-foundation.org> wrote:
> >> On Fri, 15 May 2009, Ray Lee wrote:
> >>
> >>> Which kernel version? If it's something recent, your programs may be
> >>> getting swapped out due to a flaw in the latest kernels, where it
> >>> accidentally prefers caching file data over mapped pages. If that's
> >>> the case, Rik (cc:d) is working on patches to address the issue, and
> >>> may appreciate another tester.
> >> Please keep me in the loop. I'd be interested if those patches work and
> >> what effect they have.
> >
> > Whoops, looks like Wu Fengguang (cc:d), not Rik, has been working on
> > those patches. See the messages starting with "[PATCH 0/3] make mapped
> > executable pages the first class citizen" [
> > http://lkml.org/lkml/2009/5/16/23 ]
>
> We both have. Wu's patches build on a patch of mine, which
> Andrew has already merged into -mm.
>
> http://lkml.org/lkml/2009/4/29/489
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?
Thanks,
Fengguang
next prev parent reply other threads:[~2009-05-17 1:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 17:07 unresponsiveness on linux desktop during file copy 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 [this message]
2009-05-17 1:27 ` Satish Eerpini
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=20090517011906.GA6375@localhost \
--to=fengguang.wu@intel.com \
--cc=cl@linux-foundation.org \
--cc=eerpini@gmail.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