From: Ulrich Drepper <drepper@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: yoshfuji@linux-ipv6.org, netdev@vger.kernel.org
Subject: Re: [RFC] [GIT PATCH net-2.6.23] IPV6: Configurable IPv6 address selection policy table (RFC3484)
Date: Sun, 29 Apr 2007 12:43:21 -0700 [thread overview]
Message-ID: <4634F559.10603@redhat.com> (raw)
In-Reply-To: <20070429.120218.115910157.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
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 ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
prev parent reply other threads:[~2007-04-29 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 7:28 [RFC] [GIT PATCH net-2.6.23] IPV6: Configurable IPv6 address selection policy table (RFC3484) YOSHIFUJI Hideaki / 吉藤英明
2007-04-29 6:17 ` David Miller
2007-04-29 6:39 ` Ulrich Drepper
2007-04-29 19:02 ` David Miller
2007-04-29 19:43 ` Ulrich Drepper [this message]
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=4634F559.10603@redhat.com \
--to=drepper@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--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).