From: kuznet@ms2.inr.ac.ru
To: drepper@redhat.com (Ulrich Drepper)
Cc: netdev@oss.sgi.com, yoshfuji@linux-ipv6.org, kuznet@ms2.inr.ac.ru
Subject: Re: RFC 3484 support
Date: Thu, 13 Nov 2003 13:07:57 +0300 (MSK) [thread overview]
Message-ID: <200311131007.NAA23770@yakov.inr.ac.ru> (raw)
In-Reply-To: <3FB18758.8040708@redhat.com> from "Ulrich Drepper" at îÏÑ 11, 2003 05:05:28
Hello!
> To sort the destination addresses the source address for each of the
> addresses returned by getaddrinfo must be determined. This can be done
> in two ways:
>
> 1. use the existing kernel functionality and provide an interface to it
> which userlevel can use
This interface is connect() for example. Essentially, connect() on
datagram socket with subsequent getsockname() makes exactly this.
> #2 above has serious problems.
This is just impossible.
> the kernel? Could we get a syscall or whatever to pass down to the
> kernel a set of addresses (and whatever else is needed) and the kernel
> passing back information about the sorted list (either the sorting list
> or a transformation description of some sort)?
Do you really need this?
Right now the kernel is able to to determine a valid source address
derived from some known destination address and nothing more. It is
just connect().
I do not understand rfc3484, actually. Does it involve some policies made
inside libc, which could contradict to policies used by kernel? If so,
it is definitely unimplementable without surgery in the kernel.
Alexey
next prev parent reply other threads:[~2003-11-13 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 1:05 RFC 3484 support Ulrich Drepper
2003-11-13 10:07 ` kuznet [this message]
2003-11-13 13:26 ` Pekka Savola
2003-11-13 23:17 ` Ulrich Drepper
2003-11-13 23:29 ` Pekka Savola
2003-11-13 23:12 ` Ulrich Drepper
2003-11-14 23:45 ` kuznet
2003-11-18 8:59 ` Ulrich Drepper
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=200311131007.NAA23770@yakov.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=drepper@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.org \
/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).