Hello all,
If I understood the code correctly, in fq_pie there is a single PIE
instance that controls all "fq" queues. In contrast in fq_codel there is
a separate instance of codel for each queue. Is this the case? If it is,
doesn't it contradict with original idea of fq_something where each
queue is supposed to be managed by "its own" AQM?
Thanks in advance,
Best Regards,
Polina
On 06/05/2015 12:06 AM, 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
hok...@cisco.com
_______________________________________________
aqm mailing list
aqm@ietf.org
https://www.ietf.org/mailman/listinfo/aqm
