RE: [squid-users] disk replacement algo source code

Hi Henrik,
        I understand how the replacement policies work on the in-memory
objects and StoreEntry's. What I don't understand is how (where in the src
code) is this situation handled -- Say, I have configured my Squid to use a
'cache-dir' of 100MB. All of this has been filled, but none of the content
has expired, hence not been flushed out by 'swapMaintainSpace'. What happens
if a new file needs to be opened on the filesystem for new incoming content?
        If my understanding so far is correct, StoreEntry is just a sort of
index in memory for objects on the disk, and releasing a StoreEntry doesn't
effect the actual stored object. Am I right?

Thanks,
Sadhna.

> -----Original Message-----
> From: ext Henrik Nordstrom [mailto:hno@hem.passagen.se]
> Sent: Wednesday,June 06,2001 4:02 PM
> To: Sadhna.Ahuja@nokia.com
> Cc: squid-users@squid-cache.org
> Subject: Re: [squid-users] disk replacement algo source code
>
>
> See programmers guide. The guide for Squid-2.5 contains a section on
> removal policies and how these are used by memory and stores.
>
> --
> Henrik Nordstrom
>
> Sadhna.Ahuja@nokia.com wrote:
> >
> > Hi,
> > I am trying to understand some implementation
> details of Squid. I
> > have tried, but failed to find the source code related to the disk
> > replacement algorithm. I can see when data is flushed out
> of the memory, and
> > how expired items are released from the cache by running the
> > swapMaintainSpace event. But I am interested in seeing when
> (and where in
> > the source code) does disk replacement come into play.
> > Could someone please point out some routines I
> should look at?
> >
> > Thanks a lot,
> > Sadhna.
>
Received on Mon Jun 11 2001 - 08:33:05 MDT