Bug 1261520

Summary:	Missing manpage for tc fq
Product:	Red Hat Enterprise Linux 7	Reporter:	Jaroslav Aster <jaster>
Component:	iproute	Assignee:	Phil Sutter <psutter>
Status:	CLOSED ERRATA	QA Contact:	Jaroslav Aster <jaster>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.3	CC:	kzhang, rkhan
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	iproute-3.10.0-58.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-03 23:34:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1301628, 1313485

Description Jaroslav Aster 2015-09-09 14:04:39 UTC

Description of problem:

New queue, fq, was added into tc, but there is no manpage for that queue, like tc-sfq, tc-pfifo, so user has no change to get more information about queue.


Version-Release number of selected component (if applicable):

iproute-3.10.0-53.el7

Comment 1 Phil Sutter 2016-01-12 17:43:15 UTC

Following upstream commits need to be backported:

commit 484b3f922cfd5a38a73de5981e471f99ecfe3e8b
Author: Florian Westphal <fw>
Date:   Thu Sep 24 02:10:28 2015 +0200

    man: tc: add man page for fq pacer
    
    Partially based on kernel Kconfig help text, code comments and
    git commit messages from Eric Dumazet.
    
    Joint work with Phil Sutter.
    
    Signed-off-by: Phil Sutter <phil>
    Signed-off-by: Florian Westphal <fw>


commit e947d8947d34114e2ea7c5508dfbb9b10b4611c2
Author: Stephen Hemminger <stephen>
Date:   Wed Jan 6 10:29:06 2016 -0800

    man: fix whatis for fq
    
    The FQ man page was not following whatis formatting rules.

Comment 6 errata-xmlrpc 2016-11-03 23:34:01 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2162.html