__pdflush have an unnecessary code ?

From: barrios <hidden>
Date: 2007-07-19 14:15:36
Also in: lkml
Subsystem: memory management, the rest · Maintainers: Andrew Morton, Linus Torvalds

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 */
               }
       }
--

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help