{"id":3148,"date":"2022-12-20T16:43:37","date_gmt":"2022-12-20T19:43:37","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/tc-man8-4\/"},"modified":"2022-12-20T16:43:37","modified_gmt":"2022-12-20T19:43:37","slug":"tc-man8-4","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/tc-man8-4\/","title":{"rendered":"TC (man8)"},"content":{"rendered":"<h1 align=\"center\">TC<\/h1>\n<p> <a href=\"#NAME\">NAME<\/a><br \/> <a href=\"#SYNOPSIS\">SYNOPSIS<\/a><br \/> <a href=\"#DESCRIPTION\">DESCRIPTION<\/a><br \/> <a href=\"#ALGORITHM\">ALGORITHM<\/a><br \/> <a href=\"#PARAMETERS\">PARAMETERS<\/a><br \/> <a href=\"#SOURCE\">SOURCE<\/a><br \/> <a href=\"#SEE ALSO\">SEE ALSO<\/a><br \/> <a href=\"#AUTHOR\">AUTHOR<\/a> <\/p>\n<hr>\n<h2>NAME <a name=\"NAME\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">choke \u2212 choose and keep scheduler<\/p>\n<h2>SYNOPSIS <a name=\"SYNOPSIS\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>tc qdisc &#8230; choke limit<\/b> packets <b>min<\/b> packets <b>max<\/b> packets <b>avpkt<\/b> bytes <b>burst<\/b> packets <b>[ ecn ] [ bandwidth<\/b> rate <b>] probability<\/b> chance<\/p>\n<h2>DESCRIPTION <a name=\"DESCRIPTION\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">CHOKe (CHOose and Keep for responsive flows, CHOose and Kill for unresponsive flows) is a classless qdisc designed to both identify and penalize flows that monopolize the queue. CHOKe is a variation of RED, and the configuration is similar to RED.<\/p>\n<h2>ALGORITHM <a name=\"ALGORITHM\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">Once the queue hits a certain average length, a random packet is drawn from the queue. If both the to-be-queued and the drawn packet belong to the same flow, both packets are dropped. Otherwise, if the queue length is still below the maximum length, the new packet has a configurable chance of being marked (which may mean dropped). If the queue length exceeds <b>max<\/b>, the new packet will always be marked (or dropped). If the queue length exceeds <b>limit<\/b>, the new packet is always dropped.<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\">The marking probability computation is the same as used by the RED qdisc.<\/p>\n<h2>PARAMETERS <a name=\"PARAMETERS\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">The parameters are the same as for RED, except that RED uses bytes whereas choke counts packets. See <b>tc-red<\/b>(8) for a description.<\/p>\n<h2>SOURCE <a name=\"SOURCE\"><\/a> <\/h2>\n<table width=\"100%\" border=\"0\" rules=\"none\" frame=\"void\" cellspacing=\"0\" cellpadding=\"0\">\n<tr valign=\"top\" align=\"left\">\n<td width=\"11%\"><\/td>\n<td width=\"1%\">\n<p style=\"margin-top: 1em\">o<\/p>\n<\/td>\n<td width=\"10%\"><\/td>\n<td width=\"78%\">\n<p style=\"margin-top: 1em\">R. Pan, B. Prabhakar, and K. Psounis, &#8220;CHOKe, A Stateless Active Queue Management Scheme for Approximating Fair Bandwidth Allocation&#8221;, IEEE INFOCOM, 2000.<\/p>\n<\/td>\n<\/tr>\n<tr valign=\"top\" align=\"left\">\n<td width=\"11%\"><\/td>\n<td width=\"1%\">\n<p>o<\/p>\n<\/td>\n<td width=\"10%\"><\/td>\n<td width=\"78%\">\n<p>A. Tang, J. Wang, S. Low, &#8220;Understanding CHOKe: Throughput and Spatial Characteristics&#8221;, IEEE\/ACM Transactions on Networking, 2004<\/p>\n<\/td>\n<\/tr>\n<\/table>\n<h2>SEE ALSO <a name=\"SEE ALSO\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>tc<\/b>(8), <b>tc-red<\/b>(8)<\/p>\n<h2>AUTHOR <a name=\"AUTHOR\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">sched_choke was contributed by Stephen Hemminger.<\/p>\n<hr>\n","protected":false},"excerpt":{"rendered":"<p>  choke \u2212 choose and keep scheduler <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,4,292],"class_list":["post-3148","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-man8","tag-tc-choke"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3148","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3148"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3148\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3148"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3148"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3148"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}