Re: High CPU load with pcscd and Kerkey security Module
Oliver Graute <[email protected]> Tue, 22 Nov 2016 09:40:13 +0100
| Newsgroups | gmane.comp.lib.muscle |
|---|---|
| Message-ID | <CA+KjHfZVFMBUhb_fKpxTJ5y6o0i7QpTi=Th0mDqgup3TeH8FvA@mail.gmail.com> |
On Mon, Nov 21, 2016 at 1:08 PM, Ludovic Rousseau <[email protected]> wrote: > 2016-11-21 11:47 GMT+01:00 Oliver Graute <[email protected]>: >> Many thanks for your analysis and your comment. >> My pcscd-spy debugging leads to similar results >> >> Results sorted by total execution time >> total time: 597.958052 sec >> 42.015016 sec (308 calls) 7.03% SCardTransmit >> 9.974089 sec (1687 calls) 1.67% SCardStatus > > I guess this list is trunated, right? > Can you share the complete results? Results sorted by total execution time total time: 597.958052 sec 1.260111 sec ( 14 calls) 0.21% SCardTransmit 0.437992 sec ( 37 calls) 0.07% SCardStatus 0.058914 sec ( 3 calls) 0.01% SCardEndTransaction 0.031738 sec ( 4 calls) 0.01% SCardGetStatusChange 0.016146 sec ( 1 calls) 0.00% SCardEstablishContext 0.015728 sec ( 2 calls) 0.00% SCardConnect 0.008783 sec ( 3 calls) 0.00% SCardBeginTransaction 0.004295 sec ( 3 calls) 0.00% SCardListReaders 0.000688 sec ( 1 calls) 0.00% SCardDisconnect Results sorted by total execution time total time: 597.958052 sec 42.015016 sec (308 calls) 7.03% SCardTransmit 9.974089 sec (1687 calls) 1.67% SCardStatus 3.144835 sec (278 calls) 0.53% SCardEndTransaction 2.814056 sec (123 calls) 0.47% SCardGetStatusChange 1.173591 sec (278 calls) 0.20% SCardBeginTransaction 0.226849 sec ( 4 calls) 0.04% SCardConnect 0.047858 sec ( 2 calls) 0.01% SCardEstablishContext 0.032616 sec ( 6 calls) 0.01% SCardListReaders 0.019015 sec ( 4 calls) 0.00% SCardDisconnect 0.004632 sec ( 2 calls) 0.00% SCardReleaseContext I don't now why I got two results sets here. >>> Are you the author of the PC/SC application running on your board? >> >> No, we are using a custom libpkk11 PKCS11# Host middleware on >> top of pcscd, unfortunately this lib is closed source for me. So I need to >> contact the Libkkp11 team (ST Microsystem) to investigate this further. > > Good luck with proprietary software :-)