Return-Path: william@bourbon.usc.edu
Delivery-Date: Sat Apr 21 20:25:08 2007
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on merlot.usc.edu
X-Spam-Level: 
X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,
	NO_REAL_NAME autolearn=ham version=3.1.3
Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75])
	by merlot.usc.edu (8.13.5/8.13.5) with ESMTP id l3M3P8GO014355
	for <cs551@merlot.usc.edu>; Sat, 21 Apr 2007 20:25:08 -0700
Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1])
	by bourbon.usc.edu (8.13.5/8.13.5) with ESMTP id l3M3OtMY002590
	for <cs551@merlot>; Sat, 21 Apr 2007 20:24:55 -0700
Message-Id: <200704220324.l3M3OtMY002590@bourbon.usc.edu>
To: cs551@merlot.usc.edu
Subject: Re: About LRU 
Date: Sat, 21 Apr 2007 20:24:55 -0700
From: william@bourbon.usc.edu

Someone wrote:

  > LRU list is updated
  > At the sender(which sent the msg) node when:
  > originating store?
  > successful get?

If you originate a STORE or afer a successful GET, the
file you just got should be put at the end of the LRU
list.  If you already have the file in the GET case, then
you should move the file to the end of the LRU list.

  > At the receiver(which sent the response) node:
  > receiving store?
  > receiving get?

Again, when you STORE a file, you put it at the end of
the LRU list.  You don't need to do anything when you
get a GET.  You need to move a file to the end of the
LRU list if it matches a SEARCH request.

  > At intermediate nodes(just fwding msgs or responses):
  > fwding get response?

Intermediate nodes do nothing (as far as I can think of).
--
Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>




  ----- Original Message -----
  From: william@bourbon.usc.edu
  Date: Thursday, April 12, 2007 11:44 am
  Subject: Re: About LRU
  To: cs551@merlot.usc.edu
  
  > Hi,
  > 
  > Just want to clarify...  What I thought the question was
  > about your index structure to keep track of LRU.  That has no
  > limit.  Certainly, the total size of the cahced data file (you
  > don't have to count metadata and certificate file sizes, and
  > it's okay if you do) has a limit which is specified by the
  > CacheSize key in the startup configuration file.
  > --
  > Bill Cheng // bill.cheng@usc.edu 
  > <URL:http://merlot.usc.edu/william/usc/>
  > 
  > 
  >  -----Original Message-----
  >  Date: Sat, 07 Apr 2007 16:18:43 -0700
  >  From: william@bourbon.usc.edu
  >  To: cs551@merlot.usc.edu
  >  Subject: Re: About LRU 
  > 
  >  Someone wrote:
  >  
  >    > What is the size limit for cache used in implementing
  >    > LRU? (e.g. bytes or number of files).
  >  
  >  There is no limit.
  >  --
  >  Bill Cheng // bill.cheng@usc.edu 
  > <URL:http://merlot.usc.edu/william/usc/>