public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Satish Eerpini <eerpini@gmail.com>
Cc: Wu Fengguang <fengguang.wu@intel.com>,
	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: Sat, 16 May 2009 21:57:19 -0700	[thread overview]
Message-ID: <20090516215719.1fe0d583@infradead.org> (raw)
In-Reply-To: <93655eb70905162130k13ebd627o5eba2582508a1c07@mail.gmail.com>

On Sun, 17 May 2009 10:00:28 +0530
Satish Eerpini <eerpini@gmail.com> wrote:

> > I've prepared a rolled up patch for you, run time tested.  It should
> > protect all of the above pages from being evicted by large file
> > copies.
> >
> > The attached patch is for 2.6.29.
> 
> I applied the patch , but the number don seem to show much difference
> , following are the statistics with the patched kernel, could
> something else be causing the huge iowait,  :
> 


for i in `pidof kjournald` ; do ionice -c1 -p $i ; done

is another thing to try to fix the responsiveness...

-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2009-05-17  4:57 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
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 [this message]
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=20090516215719.1fe0d583@infradead.org \
    --to=arjan@infradead.org \
    --cc=cl@linux-foundation.org \
    --cc=eerpini@gmail.com \
    --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