netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Olga Albisser <olgabnd@gmail.com>, netdev@vger.kernel.org
Cc: Olga Albisser <olga@albisser.org>,
	Koen De Schepper <koen.de_schepper@nokia-bell-labs.com>,
	Oliver Tilmans <olivier.tilmans@nokia-bell-labs.com>,
	Bob Briscoe <research@bobbriscoe.net>,
	Henrik Steen <henrist@henrist.net>
Subject: Re: [PATCH net-next] sched: add dualpi2 scheduler module
Date: Thu, 14 Mar 2019 17:48:57 +0100	[thread overview]
Message-ID: <87wol1xuyu.fsf@toke.dk> (raw)
In-Reply-To: <20190311151455.3436-1-olga@albisser.org>

Olga Albisser <olgabnd@gmail.com> writes:

> DUALPI2 provides extremely low latency & loss to traffic that uses a
> scalable congestion controller (e.g. L4S, DCTCP) without degrading the
> performance of 'classic' traffic (e.g. Reno, Cubic etc.). It is intended
> to be the reference implementation of the IETF's DualQ Coupled AQM.

Hi Olga

I noticed that there's an IPR disclosure filed at the IETF[0] claiming a
patent on the algorithm. I'm curious if you know whether Nokia has an
official position on the use of that patent in this implementation if it
becomes part of the kernel? :)

-Toke

[0] https://datatracker.ietf.org/ipr/2952/

  parent reply	other threads:[~2019-03-14 16:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 15:14 [PATCH net-next] sched: add dualpi2 scheduler module Olga Albisser
2019-03-11 15:41 ` Eric Dumazet
     [not found]   ` <CANFQ_ZhUOXwiWhmgzN227htWh5Wxg5PHBxHNp=T1Z8YTu-=O5w@mail.gmail.com>
2019-03-11 16:08     ` Eric Dumazet
2019-03-11 16:03 ` Eric Dumazet
2019-03-11 16:12   ` Eric Dumazet
2019-03-11 22:13 ` kbuild test robot
2019-03-14 16:48 ` Toke Høiland-Jørgensen [this message]
2019-03-14 17:18   ` Tilmans, Olivier (Nokia - BE/Antwerp)
2019-03-14 21:18     ` 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

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

  git send-email \
    --in-reply-to=87wol1xuyu.fsf@toke.dk \
    --to=toke@redhat.com \
    --cc=henrist@henrist.net \
    --cc=koen.de_schepper@nokia-bell-labs.com \
    --cc=netdev@vger.kernel.org \
    --cc=olga@albisser.org \
    --cc=olgabnd@gmail.com \
    --cc=olivier.tilmans@nokia-bell-labs.com \
    --cc=research@bobbriscoe.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).