Open
Bug 265620
Opened 20 years ago
Updated 2 years ago
Use buffer to reduce C_DigestUpdate calls to Cryptoki during SSL handshake
Categories
(NSS :: Libraries, enhancement, P2)
Tracking
(Not tracked)
NEW
People
(Reporter: bugz, Unassigned)
Details
(Keywords: perf)
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
David Jacobson requested that we buffer calls to C_DigestUpdate when the message
size was a few bytes. He believes these calls have an adverse effect on token
performance.
I implemented a quick patch that tried to do this. Julien later found a crash
in a tree with that patch intact (bug 262192). However, it is not clear if the
patch was responsible. In the course of that bug Nelson fixed an unrelated bug
in my patch.
This bug is to track David's original enhancement request.
Comment 1•20 years ago
|
||
Comment 2•20 years ago
|
||
I know we have similiar code in CMS because tokens tend to have high latency
between calls. On the other hand, you get better response with smaller buffers
in software. In the CMS case we look at the PKCS #11 is hardware flag to
determine if we are going to buffer or not.
I'm not sure it's the same situation here (it may be better to just always
buffer), I suggest trying some profiling to make sure our memory consumption
does not drastically increase in the software case. If it does, we should only
buffer (and allocate the space for buffers) if digesting to a slot with the HW
flag set.
bob
Updated•20 years ago
|
Priority: -- → P2
Target Milestone: --- → 3.10
Updated•20 years ago
|
QA Contact: bishakhabanerjee → jason.m.reid
Comment 3•19 years ago
|
||
Julien, feel free to reassign the bug to some
other Sun NSS developer.
Assignee: wtchang → julien.pierre.bugs
Target Milestone: 3.10 → 3.12
Updated•19 years ago
|
QA Contact: jason.m.reid → libraries
Comment 4•16 years ago
|
||
Unsetting target milestone in unresolved bugs whose targets have passed.
Target Milestone: 3.12 → ---
Updated•15 years ago
|
Assignee: julien.pierre.boogz → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•