__pdflush have an unnecessary code ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux