General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Bill Ver Steeg (versteb)" <versteb@cisco.com>
To: Simon Barber <simon@superduper.net>,
	"Hironori Okano -X (hokano - AAP3 INC at Cisco)"
	<hokano@cisco.com>,
	"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>,
	"aqm@ietf.org" <aqm@ietf.org>
Cc: "Rong Pan \(ropan\)" <ropan@cisco.com>,
	"Preethi Natarajan \(prenatar\)" <prenatar@cisco.com>
Subject: Re: [Bloat] FQ-PIE kernel module implementation
Date: Mon, 8 Jun 2015 10:14:36 +0000	[thread overview]
Message-ID: <AE7F97DB5FEE054088D82E836BD15BE931A3353A@xmb-aln-x05.cisco.com> (raw)
In-Reply-To: <5571E450.7090209@superduper.net>

[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]

The legal answer is "read the IPR disclosure at the IETF" and "read the copy write notice in the code".

I think that you will like what you find, though....... The broad intent is to fix the bloat problem in as many places as possible.

Bill VerSteeg

From: bloat-bounces@lists.bufferbloat.net [mailto:bloat-bounces@lists.bufferbloat.net] On Behalf Of Simon Barber
Sent: Friday, June 05, 2015 8:03 PM
To: Hironori Okano -X (hokano - AAP3 INC at Cisco); bloat@lists.bufferbloat.net; aqm@ietf.org
Cc: Rong Pan (ropan); Preethi Natarajan (prenatar)
Subject: Re: [Bloat] FQ-PIE kernel module implementation

Very cool. Does this mean that Cisco are not planning on enforcing any IP rights over PIE?

Simon
On 6/4/2015 3:06 PM, Hironori Okano -X (hokano - AAP3 INC at Cisco) wrote:
Hi all,

I'm Hironori Okano and Fred's intern.
I'd like to let you know that I have implemented FQ-PIE as a linux kernel module "fq-pie" and iproute2 for fq-pie.
This was done in collaboration with others at Cisco including Fred Baker, Rong Pan, Bill Ver Steeg, and Preethi Natarajan.

The source codes are in my github repository. I attached patch file "fq-pie_patch.tar.gz" to this email also.
I'm using the latest linux kernel (git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git)

fq-pie kernel module
https://github.com/hironoriokano/fq-pie.git

iproute2 for fq-pie
https://github.com/hironoriokano/iproute2_fq-pie.git

If you have any comments, please reach out to me.

Best regards,

Hironori Okano
hokano@cisco.com<mailto:hokano@cisco.com>




_______________________________________________

Bloat mailing list

Bloat@lists.bufferbloat.net<mailto:Bloat@lists.bufferbloat.net>

https://lists.bufferbloat.net/listinfo/bloat


[-- Attachment #2: Type: text/html, Size: 6929 bytes --]

  reply	other threads:[~2015-06-08 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 22:06 Hironori Okano -X (hokano - AAP3 INC at Cisco)
2015-06-04 22:18 ` [Bloat] [aqm] " Dave Taht
2015-06-05 18:02 ` [Bloat] " Simon Barber
2015-06-08 10:14   ` Bill Ver Steeg (versteb) [this message]
2015-06-08 10:21     ` Bill Ver Steeg (versteb)
2015-06-17 20:17   ` [Bloat] [aqm] " Fred Baker (fred)

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/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=AE7F97DB5FEE054088D82E836BD15BE931A3353A@xmb-aln-x05.cisco.com \
    --to=versteb@cisco.com \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=hokano@cisco.com \
    --cc=prenatar@cisco.com \
    --cc=ropan@cisco.com \
    --cc=simon@superduper.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