From: Dan McDonald <danmcd@nexenta.com>
To: "Dave Täht" <d@taht.net>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: branching the kernel, etc.
Date: Sun, 6 Feb 2011 16:01:56 -0500 [thread overview]
Message-ID: <20110206210156.GA72677@mactavish> (raw)
In-Reply-To: <87ipwxf31b.fsf@cruithne.co.teklibre.org>
On Sun, Feb 06, 2011 at 11:09:36AM -0700, Dave Täht wrote:
<SNIP!>
> * Different solutions for different OSes
>
> Related to all that is recruiting a BSD person, MS person, embedded
> person, etc into the herd of cats.
I'm lurking here on behalf of Illumos (the fork from formerly-Open Solaris).
In Illumos we can exert a *bit* more quality control, but most Illumos
developers have day jobs not *directly* related to the TCP/IP stack.
In other words, I have no time to contribute data. I can, given solid
measurements, sway the powers-that-be in Illumos to possibly take in
appropriate changes.
Dan
next prev parent reply other threads:[~2011-02-06 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 18:09 Dave Täht
2011-02-06 21:01 ` Dan McDonald [this message]
2011-02-08 16:30 ` [Bloat] " John W. Linville
2011-02-08 17:59 ` Eric Raymond
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=20110206210156.GA72677@mactavish \
--to=danmcd@nexenta.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=d@taht.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