incubator-directmemory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tommaso Teofili <tommaso.teof...@gmail.com>
Subject Re: Eviction at MemoryBuffer vs at CacheService level
Date Thu, 29 Dec 2011 18:32:32 GMT
+1

Tommaso

2011/12/29 Raffaele P. Guidi <raffaele.p.guidi@gmail.com>

> Totally agreed. It's a long due refactoring
> Il giorno 29/dic/2011 17:33, "Benoit Perroud" <benoit@noisette.ch> ha
> scritto:
>
> > Hi All,
> >
> > I thought at the evicition policy. It is actually done at MemoryBuffer
> > level, but this leads to a problem :
> >
> > A pointer could be evicted, but the cache still reference it. It seems
> > to be processed correctly by the CacheService.
> >
> > My point hier is we should try to do a better separation of the
> > responsabilities, in order to have layers that could be reused
> > independently :
> >
> > - MemoryService should only try to reduce fragmentation (for example
> > using the read only buffer (see DIRECTMEMORY-9))
> > - CacheService should allow pluggable eviction (LRU, LFU, ...)
> >
> > What is your thoughts on this ?
> >
> > Thanks
> >
> > Benoit.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message