Searched refs:issue (Results 1 – 9 of 9) sorted by relevance
121 static inline u64 bio_issue_time(struct bio_issue *issue) in bio_issue_time() argument123 return __bio_issue_time(issue->value); in bio_issue_time()126 static inline sector_t bio_issue_size(struct bio_issue *issue) in bio_issue_size() argument128 return ((issue->value & BIO_ISSUE_SIZE_MASK) >> BIO_ISSUE_SIZE_SHIFT); in bio_issue_size()131 static inline void bio_issue_init(struct bio_issue *issue, in bio_issue_init() argument135 issue->value = ((issue->value & BIO_ISSUE_RES_MASK) | in bio_issue_init()
55 if (rqos->ops->issue) in rq_qos_issue()56 rqos->ops->issue(rqos, rq); in rq_qos_issue()
218 u64 now, issue = READ_ONCE(rwb->sync_issue); in rwb_sync_issue_lat() local220 if (!issue || !rwb->sync_cookie) in rwb_sync_issue_lat()224 return now - issue; in rwb_sync_issue_lat()780 .issue = wbt_issue,
30 void (*issue)(struct rq_qos *, struct request *); member
450 struct bio_issue *issue, u64 now, in iolatency_record_time() argument454 u64 start = bio_issue_time(issue); in iolatency_record_time()
37 If backward compatibility is not an issue, then it is safe and102 issue, then it is safe and recommended to say Y here.
41 to address the fair crediting issue in the next GPL version.)
371 A serious problem is that there is no documented way to issue
391 defined weak to work around addressing range issue which