[Pvfs2-developers] client caches

[Walter Ligon]

LOL, ok, that's what I was thinking.  How about cap_cache for 
capabilities?  Or do you not like the underline?

Walt

Rob Ross wrote:
> let's try to use at least two letters to describe what kind of data we 
> are caching, from now on. -- rob
> 
> On Jul 1, 2008, at 11:05 AM, Sam Lang wrote:
> 
>>
>> Hi Walt,
>>
>> The acache (attribute cache) and ncache (name cache) are both based on 
>> a generic timeout cache interface (tcache).  It shouldn't be hard to 
>> build up a capability cache using tcache, and will allow you to handle 
>> timeouts for capabilities separate from the attributes, which I would 
>> imagine you're going to want to do.  There's a good chance Rob will 
>> explode if you call it ccache though.
>>
>> -sam
>>
>> On Jul 1, 2008, at 10:56 AM, Walter Ligon wrote:
>>
>>> Hey all,
>>>
>>> I'm not an expert on the a-cache and d-cache, so I wanted to get some 
>>> opinion from the group before diving into something.  We are going to 
>>> need to manage capabilities on the client.  My gut intuition say they 
>>> should go in the a-cache, but I don't know how a big a deal it is to 
>>> add an arbitrary sized blob into that.  Would it be better to create 
>>> a new c-cache, or should it be easy enough to add it to the a-cache?
>>>
>>> Any hints would be appreciated.
>>>
>>> Walt