[15590] in Kerberos_V5_Development
Re: Project review: Parallel KDC
daemon@ATHENA.MIT.EDU (Simo Sorce)
Fri Mar 12 11:34:56 2010
Date: Fri, 12 Mar 2010 11:34:50 -0500
From: Simo Sorce <ssorce@redhat.com>
To: krbdev@mit.edu
Message-ID: <20100312113450.6cc41aa5@willson.li.ssimo.org>
In-Reply-To: <20100311225455.GM19297@Sun.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Thu, 11 Mar 2010 16:54:55 -0600
Nicolas Williams <Nicolas.Williams@sun.com> wrote:
> - The reply cache is less important if you can handle many concurrent
> requests. A per-KDC reply cache would be fine. Alternatively
> using a replay cache where each request/reply pair is stored in an
> individual file named after a hash of the request, with each file
> created with O_EXCL. This would move all locking to the filesystem
> (which should be tmpfs).
What's wrong with shared memory (eventually persistent on a file using
mmap) and mutexes or byte range loking if you want to use a database
style format ?
Simo.
--
Simo Sorce * Red Hat, Inc * New York
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
