public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Satish Eerpini <eerpini@gmail.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 17:30:04 +0800	[thread overview]
Message-ID: <20090517093004.GA2635@localhost> (raw)
In-Reply-To: <93655eb70905162318oeccafa9p76b5594f9625aefc@mail.gmail.com>

On Sun, May 17, 2009 at 02:18:01PM +0800, Satish Eerpini wrote:
> > The numbers listed in your email? No the most relevant numbers are
> > memory and disk ones.
> 
> the numbers I earlier mentioned were the output of : "sar"
> for the number of mapped pages stays almost constant on my lappy too :
> Mapped:            70840 kB
> Mapped:            70860 kB
> Mapped:            70736 kB
> Mapped:            70860 kB

Hmm, how do you define/feel the unresponsiveness?  Is it related to
the currently *running* applications, or opening a *new* application?

Thanks,
Fengguang


  reply	other threads:[~2009-05-17  9:30 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
2009-05-17  4:58                 ` Wu Fengguang
2009-05-17  6:18                   ` Satish Eerpini
2009-05-17  9:30                     ` Wu Fengguang [this message]
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=20090517093004.GA2635@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