On Thu, Dec 10, 2009 at 8:54 AM, Chas Williams (CONTRACTOR)
<c...@cmf.nrl.navy.mil> wrote:
> In message 
> <db6e3f110912100538i4f7ef40fy82acdc1040463...@mail.gmail.com>,Derric
> k Brashear writes:
>>Allowing N chunks with M chunksize configured, where N*M is greater
>>than the cache size you configured seems entirely reasonable: not
>>every chunk will be filled.
>
> but they could be.  at which point afs breaks and the user will have a
> poor experience with afs -- "afs sucks".

why could they be? or rather, why does it need to work that way? i
don't see why we'd promise it being possible, or why it would need to
be.


-- 
Derrick
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info

Reply via email to