[bind10-dev] revised in-memory NSEC task plans
Michal 'vorner' Vaner
michal.vaner at nic.cz
Wed May 9 08:23:20 UTC 2012
Hello
On Tue, May 08, 2012 at 10:07:46AM -0700, JINMEI Tatuya / 神明達哉 wrote:
> As discussed in today's meeting, we seem to want to maximize the
> concurrency in handling the current NSEC-related tickets. This is my
> proposal of revised plan:
I understood it as maximizing concurrency without bringing too much overhead, as
the reason was to be able to start doing other things soon. So if we add too
much overhead, we actually slow things down. Anyway:
> - complete #1805 with a quick hack implementation. that is, maintain
> an internal table of names in the getClosestNSEC() method (either by
> hardcoding the data or allowing the test to build it), and use that
> table to identify the "previous name". this way we can start other
> tasks depending on #1805 without waiting for the completion of #1803
> and #1804. When these two tasks are completed we'll complete
> getClosestNSEC() using the getPreviousNode() interface. That part
> will be deferred to a separate task.
#1803/#1804 is in review. I think it is less work to use the interface there
even if it was to change than implementing some kind of static table. And the
chance is it could stay the same or with minor tweaks.
With regards
--
Disclaimer: this message may contain information.
Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20120509/a5341037/attachment.bin>
More information about the bind10-dev
mailing list