Multithreading the KDC server - a design

Sam Hartman hartmans at MIT.EDU
Mon Apr 11 15:14:08 EDT 2005

Hi.  I finally got a chance to actually read the design instead of
just the comments that were being made.

I probably would have chosen approach 4.1 (not surprising since I
suggested it).  We just haven't run into cases where KDC performance
requires multiple CPUs at all.

Given that you did not choose 4.1, I think the HP comments about fine
grain locking are important.  I don't undersatnd why under your
proposal the fine grain locking would be significantly harder than a
single lock.

I also agree with those who have said that recursive mutexes should be

I don't understand why TCP and UDP are handled separately.  It seems
like you would want to read the entire request in the main thread
(using non-blocking reads for TCP) and then dispatch it.

Sam Hartman
Kerberos Team Lead
MIT Information Services and Technology

More information about the krbdev mailing list