From: Mat <jackdachef@gmail.com>
To: peterz@infradead.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, piotr@hosowicz.com
Subject: Re: [PATCH 00/20] mm: Preemptibility -v4
Date: Thu, 2 Sep 2010 17:36:35 +0200 [thread overview]
Message-ID: <AANLkTinFc+1wimmN3CQQzO-s3=uah8YDFzdy+Da=vsCx@mail.gmail.com> (raw)
Hi Peter,
I'm currently also testing your preemptibility patchset and have to
say that on top of 2.6.36-rc3 it really seems to make a positive
difference for me :)
since I'm only a regular (power)user utilizing linux-distributions for
my everyday work I can report only about that:
- the desktop stays very responsive even during copying, backing up
and transferring of large amounts of data (e.g. backing up 1 TB of
data via rsync between different filesystems); this includes the GUI
staying responsive, the mouse not lagging and apps opening up almost
instantaneously
- there is very little to no noticable lags or repetitions when
hearing webradio or audios during longer periods of time
- and much more
considering that 2.6.36 received several other improvements in this area
- http://lkml.org/lkml/2010/8/1/40, the patches from Wu Fengguang and
KOSAKI Motohiro
- concurrency managed workqueues
- and other performance improvements, especially VFS
may also add up to this
anyways: please consider adding this to next/mainline during the next
merge cycle
my linux-desktop didn't feel that reponsive for a long time ! ^^
if I recall correctly if felt comparably responsive when I used Con's
RSDL or SD scheduler - CFS and CFQ have made great progress in terms
of desktop usage, interactivity and delays
Regards and thanks to everyone involved in the continued improvements
in this area
Mat
next reply other threads:[~2010-09-02 15:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 15:36 Mat [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-28 14:16 [PATCH 00/20] mm: Preemptibility -v4 Peter Zijlstra
2010-08-28 14:16 ` Peter Zijlstra
2010-08-28 14:32 ` Peter Zijlstra
2010-08-28 22:28 ` David Miller
2010-08-28 22:41 ` Peter Zijlstra
2010-08-28 14:56 ` Piotr Hosowicz
2010-08-28 15:10 ` Peter Zijlstra
2010-08-28 15:17 ` Piotr Hosowicz
2010-08-28 15:23 ` Peter Zijlstra
2010-08-28 16:01 ` Piotr Hosowicz
2010-08-29 12:46 ` Piotr Hosowicz
2010-08-29 13:37 ` Peter Zijlstra
2010-08-29 13:43 ` Piotr Hosowicz
2010-08-31 14:02 ` Piotr Hosowicz
2010-08-31 14:14 ` Piotr Hosowicz
2010-09-02 14:53 ` Piotr Hosowicz
2010-08-28 15:19 ` Pekka Enberg
2010-08-28 15:27 ` Peter Zijlstra
[not found] ` <AANLkTikSm2Mq8hGNac9rpFH-3pvryw2kW57EP45Ny6Vp@mail.gmail.com>
2010-09-14 5:36 ` Alex,Shi
2010-09-14 7:42 ` Peter Zijlstra
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='AANLkTinFc+1wimmN3CQQzO-s3=uah8YDFzdy+Da=vsCx@mail.gmail.com' \
--to=jackdachef@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=piotr@hosowicz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.