Searched refs:withdraw (Results 1 – 10 of 10) sorted by relevance
| /Linux-v5.4/fs/gfs2/ |
| D | log.c | 93 bool *withdraw) in gfs2_ail1_start_one() argument
112 *withdraw = true; in gfs2_ail1_start_one()
153 bool withdraw = false; in gfs2_ail1_flush() local
162 if (gfs2_ail1_start_one(sdp, wbc, tr, &withdraw)) in gfs2_ail1_flush()
167 if (withdraw) in gfs2_ail1_flush()
197 bool *withdraw) in gfs2_ail1_empty_one() argument
211 *withdraw = true; in gfs2_ail1_empty_one()
229 bool withdraw = false; in gfs2_ail1_empty() local
233 gfs2_ail1_empty_one(sdp, tr, &withdraw); in gfs2_ail1_empty()
242 if (withdraw) in gfs2_ail1_empty()
|
| D | util.c | 259 bool withdraw) in gfs2_io_error_bh_i() argument
268 if (withdraw) in gfs2_io_error_bh_i()
|
| D | util.h | 138 bool withdraw);
|
| D | sys.c | 279 GFS2_ATTR(withdraw, 0644, withdraw_show, withdraw_store);
522 GDLM_ATTR(withdraw, 0644, wdack_show, wdack_store);
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | gfs2-uevents.txt | 57 as part of the "withdraw" mechanism. Currently this doesn't give any
|
| /Linux-v5.4/Documentation/filesystems/caching/ |
| D | object.txt | 268 withdraw the object from service, perhaps to make space, but also due to
313 This is signalled when the cache backend wants to withdraw an object.
|
| D | fscache.txt | 98 withdraw caching facilities from a file (required for (2)).
|
| D | backend-api.txt | 541 This does not actually withdraw the cache. That must be done separately.
|
| /Linux-v5.4/LICENSES/dual/ |
| D | CDDL-1.0 | 298 such 60 day period You withdraw Your claim with respect to the
|
| D | MPL-1.1 | 354 Participant, or (ii) withdraw Your litigation claim with respect to
|
