From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] modest dns fixes
Date: Thu, 19 Jan 2012 22:36:16 -0500 [thread overview]
Message-ID: <7d3ce6617d2577031ba78e65acc89b10@brasstown.quanstro.net> (raw)
i've pushed my modest dns fixes to sources in contrib quanstro/ndb.
this code has been running on my machine for a while, and i'm just
experimenting with it in more production environments.
in addition to the changes outlined before, i added some code to
terminate queries when no namserver is available. this prevents an
O(n²) lookup, where n is the number of name servers. (example
ndb/dnsdebug www.tridentaudio.co.uk; get some popcorn.)
i have specificly not addressed the database corruption problems.
these would seem at least partially to be a result of rrcopy() being
a shallow copy, and not doing anything about refcounting
subordinate or ->next records. (thus more locking would seem
not the answer.)
nor have i addressed the bio problem. making the buffer in
<ndb.h> 8k does sidestep the issue.
i hope this is useful, at least as a stopgap!
- erik
reply other threads:[~2012-01-20 3:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d3ce6617d2577031ba78e65acc89b10@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).