From: Nikita Danilov <nikita@clusterfs.com>
To: "Ananiev, Leonid I" <leonid.i.ananiev@intel.com>
Cc: Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: moving dirty pages balancing to pdfludh entirely
Date: Wed, 28 Jun 2006 15:33:37 +0400 [thread overview]
Message-ID: <17570.26897.378682.724475@gargle.gargle.HOWL> (raw)
In-Reply-To: <6694B22B6436BC43B429958787E4549802394A55@mssmsx402nb>
Ananiev, Leonid I writes:
> >From Leonid Ananiev
Hello,
>
> Moving dirty pages balancing from user to kernel thread pdfludh entirely
> reduces extra long write(2) latencies, increases performance.
>
[...]
> The benchmarks IOzone and Sysbench for file size 50% and 120% of
> RAM size on Pentium4, Xeon, Itanium have reported write and mix
> throughput increasing about 25%. The described Iozone > 0.1 sec write(2)
Results are impressive.
Wouldn't this interfere with current->backing_dev_info logic? This field
is set by __generic_file_aio_write_nolock() and checked by
may_write_to_queue() to force heavy writes to do more pageout. Maybe
pdflush threads should set this field too?
> latencies are deleted. The condition writeback_in_progress() is tested
> earlier now. As a result extra pdflush works are not created and number
> of context switches increasing is inside variation limites.
Nikita.
next prev parent reply other threads:[~2006-06-28 11:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 5:31 Ananiev, Leonid I
2006-06-28 11:33 ` Nikita Danilov [this message]
2006-07-03 17:31 ` Antonio Vargas
2006-07-03 16:43 Ananiev, Leonid I
2006-07-04 8:32 ` Nikita Danilov
2006-07-04 8:35 Ananiev, Leonid I
2006-07-04 9:44 Ananiev, Leonid I
2006-07-04 9:55 Nikita Danilov
2006-07-04 11:43 Ananiev, Leonid I
2006-07-04 11:56 ` Nikita Danilov
2006-07-04 13:07 Ananiev, Leonid I
[not found] <B41635854730A14CA71C92B36EC22AAC0541F6@mssmsx411>
2006-07-04 13:12 ` Nikita Danilov
2006-07-04 19:12 Ananiev, Leonid I
2006-07-04 20:20 ` Nikita Danilov
2006-07-04 22:24 ` Bret Towe
2006-07-05 10:20 ` Nikita Danilov
2006-07-05 17:19 ` Bret Towe
2006-07-05 5:40 Ananiev, Leonid I
2006-07-05 10:17 ` Nikita Danilov
2006-07-05 14:28 Ananiev, Leonid I
2006-07-05 14:57 ` Nikita Danilov
2006-07-05 15:48 Ananiev, Leonid I
2006-07-05 18:10 Ananiev, Leonid I
2006-07-05 19:07 ` Nikita Danilov
2006-07-05 19:28 Ananiev, Leonid I
2006-07-05 20:14 ` Nikita Danilov
2006-07-05 19:50 Ananiev, Leonid I
2006-07-05 20:05 ` Nikita Danilov
2006-07-06 4:30 Ananiev, Leonid I
2006-07-06 6:34 ` Nikita Danilov
2006-07-06 11:47 Ananiev, Leonid I
2006-07-06 13:54 Ananiev, Leonid I
2006-07-06 15:16 ` Nikita Danilov
2006-07-06 16:33 Ananiev, Leonid I
2006-07-06 17:37 ` Nikita Danilov
2006-07-06 21:07 Ananiev, Leonid I
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=17570.26897.378682.724475@gargle.gargle.HOWL \
--to=nikita@clusterfs.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=leonid.i.ananiev@intel.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®