From: YOSHIFUJI Hideaki / 吉藤英明 [EMAIL PROTECTED]
Date: Thu, 19 Apr 2007 16:28:56 +0900 (JST)
We store labels only in kernel, and leave precedence in userspace
(/etc/gai.conf), so far. The name resolution library (getaddrinfo(3))
is required to be changed to try reading label information from
David Miller wrote:
One idea is to have glibc have some kind of socket open, subscribed
to a group which gets sticky events.
I don't quite yet know the context but I have to intervene: keeping
sockets open is not good. This will only cause problems.
Any interface must be memory based.
From: Ulrich Drepper [EMAIL PROTECTED]
Date: Sat, 28 Apr 2007 23:39:22 -0700
David Miller wrote:
One idea is to have glibc have some kind of socket open, subscribed
to a group which gets sticky events.
I don't quite yet know the context but I have to intervene: keeping
sockets open is
David Miller wrote:
Something more scalable has to be used.
This is where the shared-memory based event notification comes in. It
was always also meant to be used for things like this.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
signature.asc
Description:
Hello.
This is RFC(*) for supporting configurable IPv6 address selection policy
table, which is described in RFC3484.
Corresponding userspace tool is available at
http://www.linux-ipv6.org/gitweb/gitweb.cgi?p=/gitroot/ip6aspctl.git;a=summary.
We store labels only in kernel, and leave
