From: jamal <hadi@cyberus.ca>
To: Caitlin Bestler <caitlinb@broadcom.com>
Cc: Steve Wise <swise@opengridcomputing.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: RE: [PATCH 0/2][RFC] Network Event Notifier Mechanism
Date: Thu, 22 Jun 2006 18:21:37 -0400 [thread overview]
Message-ID: <1151014897.5099.29.camel@jzny2> (raw)
In-Reply-To: <54AD0F12E08D1541B826BE97C98F99F15F55E2@NT-SJCA-0751.brcm.ad.broadcom.com>
On Thu, 2006-22-06 at 15:11 -0700, Caitlin Bestler wrote:
> netdev-owner@vger.kernel.org wrote:
>
> These subscriptions are an attempt to cede full control
> of these issues back to one place, the kernel, and to
> guarantee that an offload device can never think that
> the route to to X is Y when the kernel says it is Z.
> Or that it has a different PMTU, etc.
>
Ok, so it is the routing information then that you are syncing,
correct?
> I don't have any strong opinion on the best mechanism
> for implementing these subscriptions, but having correct
> consistent networking behaviour depend on a user-mode
> relay strikes me as odd.
>
And why does it sound odd?
You will need to think about one issue:
Linux caches routing info - it is not just as simple as keeping track of
the FIB and somehow correlating that to the ARP entries.
cheers,
jamal
next prev parent reply other threads:[~2006-06-22 22:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 22:11 [PATCH 0/2][RFC] Network Event Notifier Mechanism Caitlin Bestler
2006-06-22 22:21 ` jamal [this message]
2006-06-22 22:58 ` David Miller
2006-06-23 0:56 ` jamal
2006-06-23 13:24 ` Steve Wise
2006-06-23 19:57 ` David Miller
2006-06-23 20:12 ` Steve Wise
2006-06-24 14:30 ` jamal
2006-06-26 14:34 ` Steve Wise
2006-06-27 12:44 ` jamal
-- strict thread matches above, loose matches on Subject: below --
2006-06-22 22:39 Caitlin Bestler
2006-06-21 19:48 Steve Wise
2006-06-21 20:40 ` David Miller
2006-06-21 18:45 Steve Wise
2006-06-21 19:08 ` YOSHIFUJI Hideaki / 吉藤英明
2006-06-22 8:57 ` David Miller
2006-06-22 13:53 ` Steve Wise
2006-06-22 15:27 ` Steve Wise
2006-06-22 19:43 ` jamal
2006-06-22 20:18 ` Steve Wise
2006-06-22 20:36 ` jamal
2006-06-22 20:58 ` Steve Wise
2006-06-22 22:14 ` jamal
2006-06-23 13:11 ` Steve Wise
2006-06-22 20:40 ` Steve Wise
2006-06-22 20:56 ` jamal
2006-06-23 13:17 ` Steve Wise
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=1151014897.5099.29.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=caitlinb@broadcom.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=swise@opengridcomputing.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.