Re: Contradiction in storeCreateEntry?

From: Henrik Nordstrom <>
Date: Tue, 16 Apr 2002 16:16:26 +0200

Because there is not yet an object associated with the StoreEntry, neither in
memory or on disk.

I don't think this flag is actually used for anything useful other than being
printed in cachemgr and to assert that the code path is correct. The code
accessing StoreEntry mainly uses the ->mem_obj entry to tell if there is a
memory copy or not.

Henrik wrote:
> Hi, pals!
> Look at this line taken from "storeCreateEntry",
> storeSetMemStatus(e, NOT_IN_MEMORY);
> IMHO, a newly created object should be kept in memory
> and not kept in disk. Why assign "NOT_IN_MEMORY"
> to a missed but newly created cached object?
> I think the newly created object should be kept in memory.
> Best regards,
> George, Ma
Received on Tue Apr 16 2002 - 08:16:33 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:15:11 MST