From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] /sys/src/9/ip/ip.h
Date: Sun, 4 Oct 2009 13:28:45 -0400 [thread overview]
Message-ID: <45ad47d8b69ae705ef7fa6d83702477f@ladd.quanstro.net> (raw)
In-Reply-To: <<4fe555158822df97a22b2076cc02e52a@9netics.com>>
On Sun Oct 4 12:47:55 EDT 2009, 9nut@9netics.com wrote:
> perhaps the elimination of all traces of IL is a little too thorough?
> it seems easier to leave Logil, Logilmsg in place rather than require
> an extra (periodic) merge. one can't get by simply with bind
> before/after.
+1.
i haven't done this because there's no assurance such a patch
would be accepted so it would just result in a bigger delta,
but if netlog used an interface like flag_install (from the fs
kernel), it would be a step to seperating the protocols
riding on ip.
the protocols are currently imho too intertwined. and arp is
too bound up with ip. arp is useful even without an ip stack.
- erik
next parent reply other threads:[~2009-10-04 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<4fe555158822df97a22b2076cc02e52a@9netics.com>
2009-10-04 17:28 ` erik quanstrom [this message]
2009-10-04 16:46 Skip Tavakkolian
2009-10-04 17:17 ` Steve Simon
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=45ad47d8b69ae705ef7fa6d83702477f@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).