Messages in this thread | | | From | Dimitri Sivanich <> | Subject | Re: [PATCH]: Option to run cache reap in thread mode | Date | Fri, 18 Jun 2004 16:44:18 -0500 (CDT) |
| |
> > I'll write something: > - allow to disable the DMA kmalloc caches for archs that do not need them. > - increase the timer frequency and scan only a few caches in each timer. > - perhaps a quicker test for cache_reap to notice that nothing needs to > be done. Right now four tests are done (!flags & _NO_REAP, > ac->touched==0, ac->avail != 0, global timer not yet expired). It's > possible to skip some tests. e.g. move the _NO_REAP caches on a separate > list, replace the time_after(.next_reap,jiffies) with a separate timer. > > -- > Manfred > Thanks for addressing this. Sounds like some good improvements overall.
One question though: What about possible spinlock contention issues in the cache_reap timer processing, or is that unlikely here (even on a heavily loaded system with a large number of CPUs)?
Dimitri Sivanich <sivanich@sgi.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |