From: Hugo Santos <hsantos@av.it.pt>
To: Kazunori Miyazawa <kazunori@miyazawa.org>
Cc: yoshfuji@linux-ipv6.org, davem@davemloft.net,
netdev@vger.kernel.org, usagi-core@linux-ipv6.org
Subject: Re: Regarding offloading IPv6 addrconf and ndisc
Date: Thu, 27 Jul 2006 18:56:49 +0100 [thread overview]
Message-ID: <20060727175649.GO6026@innerghost.net> (raw)
In-Reply-To: <44C8B0B8.2010408@miyazawa.org>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
Hi,
> I'm interested in the approach. And I have a couple of comments.
> I think DAD and ND are time critical operations.
> Can the daemons process with confirming to the specs.
My tests indicate that yes, even when considering mobility scenarios
where expected times are reduced. There is always the possibility of
giving the process a priority high enough to work as well as possible
in most usages.
> even if it were swapped out?
Depending on the implementation, you may lock all or part of the
process address space so it doesn't get swapped out.
> Can we prevent the oom killer from killing the daemons?
I don't think we can prevent it, but we may adjust it's score via
/proc/pid/oom_adj as it's likeness of being killed being very reduced.
> Anyway, we have to consider Pros. and Cons of the approach.
As long as there is no impact in the current functionality and the
changes which are required from an architectual POV are acceptable by
the main developers, i don't see anything against.
Waiting for input,
Hugo
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-27 17:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 11:25 Regarding offloading IPv6 addrconf and ndisc Hugo Santos
2006-07-27 12:25 ` Kazunori Miyazawa
2006-07-27 17:56 ` Hugo Santos [this message]
2006-07-27 23:56 ` Herbert Xu
2006-07-28 1:34 ` David Miller
2006-07-28 1:45 ` Hugo Santos
2006-07-28 2:27 ` David Miller
2006-07-28 3:13 ` Hugo Santos
2006-07-28 3:20 ` David Miller
2006-07-28 3:31 ` Hugo Santos
2006-07-28 4:07 ` Stephen Hemminger
2006-07-28 8:34 ` Hugo Santos
2006-07-28 12:45 ` Jamal Hadi Salim
2006-07-29 13:34 ` Hugo Santos
2006-07-30 3:28 ` Kazunori Miyazawa
2006-07-30 11:30 ` Hugo Santos
2006-07-31 21:23 ` David Miller
2006-08-01 11:50 ` Hugo Santos
2006-08-01 21:54 ` David Miller
2006-08-01 0:16 ` Kazunori Miyazawa
2006-07-28 2:22 ` Herbert Xu
2006-07-28 2:33 ` David Miller
2006-08-01 0:31 ` Andi Kleen
2006-08-01 0:46 ` David Miller
2006-08-01 0:49 ` Roland Dreier
2006-08-01 1:24 ` Jamal Hadi Salim
2006-08-01 1:30 ` Herbert Xu
2006-08-01 1:47 ` Jamal Hadi Salim
2006-08-01 12:13 ` Hugo Santos
2006-08-01 12:00 ` Hugo Santos
2006-08-01 21:57 ` David Miller
2006-08-03 13:28 ` Ingo Oeser
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=20060727175649.GO6026@innerghost.net \
--to=hsantos@av.it.pt \
--cc=davem@davemloft.net \
--cc=kazunori@miyazawa.org \
--cc=netdev@vger.kernel.org \
--cc=usagi-core@linux-ipv6.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).