From: Nikita Danilov <nikita@clusterfs.com>
To: "Ananiev, Leonid I" <leonid.i.ananiev@intel.com>
Cc: "Bret Towe" <magnade@gmail.com>,
"Linux Kernel Mailing List" <Linux-Kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: moving dirty pages balancing to pdfludh entirely
Date: Thu, 6 Jul 2006 10:34:11 +0400 [thread overview]
Message-ID: <17580.44771.974069.737756@gargle.gargle.HOWL> (raw)
In-Reply-To: <B41635854730A14CA71C92B36EC22AAC06CFE8@mssmsx411>
Ananiev, Leonid I writes:
> Nikita Danilov writes:
> > Some people do, should they suffer? :-)
> You - yes. You have used that example as an argument incorrectly.
You are inhumane. :-) What is incorrect in assuming people may have many
devices?
>
> > Not _all_, only nr_to_write of them
> Yes. User thread writes all dirty pages in the system calling
No. User thread will not write _all_ dirty pages (if it does---it's a
bug in the current code and should be fixed):
balance_dirty_pages():
if (pages_written >= write_chunk)
break; /* We've done our duty */
writeback_inodes():
if (wbc->nr_to_write <= 0)
break;
sync_sb_inodes():
if (wbc->nr_to_write <= 0)
break;
mpage_writepages():
if (ret || (--(wbc->nr_to_write) <= 0))
done = 1;
Everywhere down call-chain ->nr_to_write is checked.
> writeback_inodes() and after it tests
> if (pages_written >= write_chunk)
[rants skipped.]
>
> Leonid
Nikita.
next prev parent reply other threads:[~2006-07-06 6:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 4:30 Ananiev, Leonid I
2006-07-06 6:34 ` Nikita Danilov [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-06 21:07 Ananiev, Leonid I
2006-07-06 16:33 Ananiev, Leonid I
2006-07-06 17:37 ` Nikita Danilov
2006-07-06 13:54 Ananiev, Leonid I
2006-07-06 15:16 ` Nikita Danilov
2006-07-06 11:47 Ananiev, Leonid I
2006-07-05 19:50 Ananiev, Leonid I
2006-07-05 20:05 ` Nikita Danilov
2006-07-05 19:28 Ananiev, Leonid I
2006-07-05 20:14 ` Nikita Danilov
2006-07-05 18:10 Ananiev, Leonid I
2006-07-05 19:07 ` Nikita Danilov
2006-07-05 15:48 Ananiev, Leonid I
2006-07-05 14:28 Ananiev, Leonid I
2006-07-05 14:57 ` Nikita Danilov
2006-07-05 5:40 Ananiev, Leonid I
2006-07-05 10:17 ` 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
[not found] <B41635854730A14CA71C92B36EC22AAC0541F6@mssmsx411>
2006-07-04 13:12 ` Nikita Danilov
2006-07-04 13:07 Ananiev, Leonid I
2006-07-04 11:43 Ananiev, Leonid I
2006-07-04 11:56 ` Nikita Danilov
2006-07-04 9:55 Nikita Danilov
2006-07-04 9:44 Ananiev, Leonid I
2006-07-04 8:35 Ananiev, Leonid I
2006-07-03 16:43 Ananiev, Leonid I
2006-07-04 8:32 ` Nikita Danilov
2006-06-27 5:31 Ananiev, Leonid I
2006-06-28 11:33 ` Nikita Danilov
2006-07-03 17:31 ` Antonio Vargas
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=17580.44771.974069.737756@gargle.gargle.HOWL \
--to=nikita@clusterfs.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=leonid.i.ananiev@intel.com \
--cc=magnade@gmail.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®