Use of pool servers reveals unacceptable crash rate in async DNS
hmurray at megapathdsl.net
Sun Jun 26 05:03:32 UTC 2016
esr at thyrsus.com said:
> In this case, we have two possible complexity-reducing fixes. One is to
> drop the memlock feature entirely. The other is to drop the buggy homebrew
> asynchronous-DNS lookup from Classic and use libc's.
Dropping memlock is an interesting idea. I can't think of any place where it
is required today but my crystal ball for what we will need tomorrow has
never been very good.
What would you do if we discovered a case where we wanted it?
We could try simplifying things to only supporting lock-everything-I-need
rather than specifying how much. There might be a slippery slope if
something like a thread stack needs a sane size specified.
Is there a simple way to count page faults for a process? Or measure swapped
out data and/or code that isn't swapped in?
I don't think your use-libc approach will be as simple as you would like. It's not available on NetBSD or FreeBSD. Maybe I just didn't look in the right place. It's not in netdb.h where it is for Linux.
These are my opinions. I hate spam.
More information about the devel