Re: [PATCH] file: kill unnecessary timer in fdtable_defer

On Sun, Aug 20, 2006 at 10:15:42PM +0900, Tejun Heo wrote:
> free_fdtable_rc() schedules timer to reschedule fddef->wq if
> schedule_work() on it returns 0.  However, schedule_work() guarantees
> that the target work is executed at least once after the scheduling
> regardless of its return value.  0 return simply means that the work
> was already pending and thus no further action was required.

Hmm.. Is this really true ? IIRC, schedule_work() checks pending
work based on bit ops on work->pending and clear_bit() is not
a memory barrier. So, if I see work->pending = 1 in free_fdtable_work(), how
do I know that the work function is already executing and
missed the new work that I had queued ?


Thanks
Dipankar
-
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/

---

• Follow-Ups:
  • Re: [PATCH] file: kill unnecessary timer in fdtable_defer
    • From: Tejun Heo <[email protected]>

• References:
  • [PATCH] file: kill unnecessary timer in fdtable_defer
    • From: Tejun Heo <[email protected]>

• Prev by Date: [PATCH] autofs4 - pending flag not cleared on mount fail
• Next by Date: Trying to make kernel thread sleep
• Previous by thread: [PATCH] file: kill unnecessary timer in fdtable_defer
• Next by thread: Re: [PATCH] file: kill unnecessary timer in fdtable_defer
• Index(es):
  • Date
  • Thread

[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]