Home
last modified time | relevance | path

Searched refs:requests (Results 1 – 9 of 9) sorted by relevance

/fs/btrfs/
DKconfig39 Adds code that examines all block write requests (including
51 to verify the integrity of (super)-block write requests
/fs/ncpfs/
Dsock.c149 while (!list_empty(&server->tx.requests)) { in __abort_ncp_connection()
150 req = list_entry(server->tx.requests.next, struct ncp_request_reply, req); in __abort_ncp_connection()
341 list_add_tail(&req->req, &server->tx.requests); in ncp_add_request()
355 if (list_empty(&server->tx.requests)) { in __ncp_next_request()
358 req = list_entry(server->tx.requests.next, struct ncp_request_reply, req); in __ncp_next_request()
Dncp_fs_sb.h136 struct list_head requests; /* STREAM only: queued requests */ member
Dinode.c613 INIT_LIST_HEAD(&server->tx.requests); in ncp_fill_super()
/fs/nfs/
Dread.c298 int requests = 0; in nfs_pagein_multi() local
314 requests++; in nfs_pagein_multi()
318 atomic_set(&req->wb_complete, requests); in nfs_pagein_multi()
Dwrite.c988 int requests = 0; in nfs_flush_multi() local
1010 requests++; in nfs_flush_multi()
1014 atomic_set(&req->wb_complete, requests); in nfs_flush_multi()
/fs/cifs/
DCHANGES53 removes 1 of 2 network requests sent on file create)
83 (readdir) requests do not get invalid results which include the now
99 when sending large SMBWriteX requests). Fix case in which a portion of
241 time out requests if server still responding reasonably fast
242 on requests on other threads. Improve POSIX locking emulation,
310 Timeout stuck requests better (where server has never responded or sent corrupt
342 requests to the server (necessary for certain applications which break with
344 requesting case insensitive matching for path based requests (requesting
443 and for the maximum number of simultaneous requests.
506 amounts of return data. Properly limit requests to MAX_REQ (50
[all …]
DREADME76 and maximum number of simultaneous requests to one server can be configured.
341 After this timeout, the cifs client requests fresh attribute
499 nobrl Do not send byte range lock requests to the server.
505 locking, send only mandatory lock requests. For some
674 system error log with the start of smb requests
701 SMB return codes while 4 enables logging of requests that take longer
702 than one second to complete (except for byte range lock requests).
706 the start of smb requests and responses can be enabled via:
/fs/xfs/
DKconfig64 from all other requests, and this can be done quite transparently