Lines Matching +full:entry +full:- +full:method
15 - mapping from IP address to client name
16 - mapping from client name and filesystem to export options
17 - mapping from UID to list of GIDs, to work around NFS's limitation
19 - mappings between local UID/GID and remote UID/GID for sites that
21 - mapping from network identify to public key for crypto authentication.
24 - general cache lookup with correct locking
25 - supporting 'NEGATIVE' as well as positive entries
26 - allowing an EXPIRED time on cache items, and removing
27 items after they expire, and are no longer in-use.
28 - making requests to user-space to fill in cache entries
29 - allowing user-space to directly set entries in the cache
30 - delaying RPC requests that depend on as-yet incomplete
31 cache entries, and replaying those requests when the cache entry
33 - clean out old entries as they expire.
36 ----------------
77 Format a request to be send to user-space for an item
85 cache entry. It is in 'buf' of length 'len'.
96 -------------
100 This will be passed to ->match to identify the target entry. If no
101 entry is found, a new entry will be create, added to the cache, and
105 if the data is valid, and may initiate an up-call to get fresh data.
106 cache_check will return -ENOENT in the entry is negative or if an up
107 call is needed but not possible, -EAGAIN if an upcall is pending,
116 revisited (->revisit). It is expected that this method will
128 ------------------
142 - a key
143 - an expiry time
144 - a content.
150 lookup fails, or when it succeeds but finds an entry that may soon
152 user-space. These requests appear in the channel file.
159 Thus a user-space helper is likely to:
170 Each cache should define a "cache_parse" method which takes a message
171 written from user-space and processes it. It should return an error
174 Each cache should also define a "cache_request" method which
181 entry will fail. This is partly for backward compatibility: The
186 -----------------------