multi buffer: completed job return guarantees #174
Labels
No labels
announcement
bug
duplicate
enhancement
help wanted
invalid
Next release
question
sighting
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-intel/isa-l_crypto#174
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Given a multi buffer manager with a runtime parallelism of
n(i.e. it can work onnbuffers in parallel), is it guaranteed that submittingnjobs will return at least one? Or does one need to submit at leastn+1jobs in the worst case (empty manager)?It seems to me that submitting
njobs is enough to get a completed job back even if the manager is empty; but I would like to get confirmation that this is indeed guaranteed.Hi @pobrn. Correct, it is guaranteed that after submitting those
njobs, you would get a completed job back, as long as you have submitted all the entire buffers (with ISAL_HASH_ENTIRE).Does this not apply regardless of the submission flags? E.g. if
ncount ofISAL_HASH_FIRSTjobs are submitted, then it is technically not guaranteed that at least one will be returned?I suppose my question really is: what is the minimum number of jobs that one needs to have so that there is always at least one that the manager does not hold on to, which can be resubmitted with further data?