* __pdflush have an unnecessary code ?
@ 2007-07-19 14:10 barrios
0 siblings, 0 replies; only message in thread
From: barrios @ 2007-07-19 14:10 UTC (permalink / raw)
To: linux-kernel, linux-mm; +Cc: akpm
When pdflush kernel thread is died, Why do it store current jiffies in
when_i_went_to_sleep variable ?
IMHO, __pdflush function have an unnecessary code although it is trivial.
If my thought is wrong, please give me a answer.
---
mm/pdflush.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/mm/pdflush.c b/mm/pdflush.c
index 8f6ee07..96aa1da 100644
--- a/mm/pdflush.c
+++ b/mm/pdflush.c
@@ -153,7 +153,6 @@ static int __pdflush(struct pdflush_work *my_work)
pdf = list_entry(pdflush_list.prev, struct pdflush_work, list);
if (jiffies - pdf->when_i_went_to_sleep > 1 * HZ) {
/* Limit exit rate */
- pdf->when_i_went_to_sleep = jiffies;
break; /* exeunt */
}
}
--
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-07-19 14:15 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-07-19 14:10 __pdflush have an unnecessary code ? barrios
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®