Re: [NET]: rt_check_expire() can take a long time, add a cond_resched()

From: Andi Kleen <[email protected]>
Date: Sat, 17 Nov 2007 13:56:08 +0100

> Arjan van de Ven <[email protected]> writes:
> >> > 
> >> > Its not that cheap. The ChangeLog included my own numbers, on a
> >> > Pentium M machine. (i686, 1.6 GHz, 1.5 GB ram)
> >> > 
> >> > Without "if (need_resched())" (so calling need_resched() X.XXX.XXX 
> >> > times), each run takes 88ms
> >> > 
> >> > With the extra check (and *much* less function calls), each run
> >> > takes 25ms
> 
> ms?!? The numbers sound wrong. Wrong unit? 

Read what Eric is saying.  He is saying "any entire run" purging
the routing cache takes that long, not just one call.
-
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/

---

• References:
  • Re: [NET]: rt_check_expire() can take a long time, add a cond_resched()
    • From: Eric Dumazet <[email protected]>
  • Re: [NET]: rt_check_expire() can take a long time, add a cond_resched()
    • From: Arjan van de Ven <[email protected]>
  • Re: [NET]: rt_check_expire() can take a long time, add a cond_resched()
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: 2.6.24-rc2-mm1 -- strange apparent network failures
• Next by Date: [PATCH] Fix PCIe double initialization bug
• Previous by thread: Re: [NET]: rt_check_expire() can take a long time, add a cond_resched()
• Next by thread: Re: [NET]: rt_check_expire() can take a long time, add a cond_resched()
• 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]