Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Tom Gundersen <teg@jklm.no>
To: Michal Schmidt <mschmidt@redhat.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] SQM in mainline openwrt, fq_codel considered for fedora default
Date: Tue, 21 Oct 2014 19:24:28 +0200	[thread overview]
Message-ID: <CAG-2HqVgYzMF9WiQOtAqPY2xXT7yG+UPZ_qjAnUCpqk-hvymXw@mail.gmail.com> (raw)
In-Reply-To: <54469242.5010506@redhat.com>

On Tue, Oct 21, 2014 at 7:05 PM, Michal Schmidt <mschmidt@redhat.com> wrote:
> On 10/21/2014 06:57 PM, Dave Taht wrote:
>> This is not the place to engage in the systemd debate.
>
> I agree. I wrote one more reply on that topic, but did not and will not
> send it.
>
>> I would appreciate some interest from the systemd folk into the work
>> of ietf  homenet, and into  things like hnetd and mdns proxy. (and the
>> reverse from those working on those concepts) The excessively dynamic
>> nature of the modern ipv6 rollout has led to a need to tightly
>> integrate address assignment,  routing and naming, which helped delay
>> barrier breaker a year and it's not clear to me to what extent the
>> modern linux server or desktop can deal with that and still provide
>> useful services, nor concepts like source specific routing, and better
>> integration with 802.11 and 802.14.
>
> Adding Tom Gundersen (the author of systemd-networkd) to CC in case he
> has any comments about this.

Thanks for the CC Michal.

I have now subscribed to cerowrt-devel (long overdue), and I would
very much appreciate any comments you guys may have on our networking
work in systemd. In particular, if there are any more tweaks like
making fq_codel the deafult, which would be the reasonable choice for
95% of users (most of whom don't know about these things and would
otherwise never touch them), we are very open to suggestions.

As pointed out earlier in this thread, systemd is obviously not a
distro, and the distros have the final say, but I think it makes sense
for us to provide reasonable default sysctl entries wherever we can
(and rather let distros override this if they want).

Cheers,

Tom

  reply	other threads:[~2014-10-21 17:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 18:56 Dave Taht
2014-10-17 19:30 ` Valdis.Kletnieks
2014-10-20 17:03   ` Dave Taht
2014-10-20 17:41     ` Valdis.Kletnieks
2014-10-21 14:50       ` Michal Schmidt
2014-10-21 16:27         ` Valdis.Kletnieks
2014-10-21 16:57           ` Dave Taht
2014-10-21 17:05             ` Michal Schmidt
2014-10-21 17:24               ` Tom Gundersen [this message]
2014-10-21 17:44                 ` Michal Schmidt
2014-10-21 17:52                   ` David Personette
2014-10-21 18:00                   ` Michal Schmidt
2014-10-21 18:06                   ` Tom Gundersen
2014-10-21 19:21                     ` Dave Taht
2014-10-21 19:51                       ` Dave Taht
2014-10-21 20:59                         ` Dave Taht
2014-12-04 16:09                           ` Tom Gundersen
2014-12-04 18:24                             ` Dave Taht
2014-10-21 23:18                 ` Toke Høiland-Jørgensen
2014-12-04 15:05                   ` Tom Gundersen
2014-12-04 15:08                     ` Toke Høiland-Jørgensen

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAG-2HqVgYzMF9WiQOtAqPY2xXT7yG+UPZ_qjAnUCpqk-hvymXw@mail.gmail.com \
    --to=teg@jklm.no \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=mschmidt@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox