From ff10f57f59314bc8b3d0d7cab39e8335f512d1d5 Mon Sep 17 00:00:00 2001 From: Alexander Duyck Date: Fri, 12 Sep 2008 17:56:50 -0700 Subject: [PATCH] --- yaml --- r: 111662 b: refs/heads/master c: 67333bb5679325db310bb612c1de3e6e47bb0043 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/networking/multiqueue.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 2ebd6deddfcf..328436514508 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: ca9b0e27e072be4cef2f5f0cbc0b0fd94eae3520 +refs/heads/master: 67333bb5679325db310bb612c1de3e6e47bb0043 diff --git a/trunk/Documentation/networking/multiqueue.txt b/trunk/Documentation/networking/multiqueue.txt index 10113ffa8072..8c2b06b77f61 100644 --- a/trunk/Documentation/networking/multiqueue.txt +++ b/trunk/Documentation/networking/multiqueue.txt @@ -68,7 +68,7 @@ the default simple_tx_hash or a custom netdev->select_queue() defined. The behavior of tc filters remains the same. However a new tc action, skbedit, has been added. Assuming you wanted to route all traffic to a -specific host, for example 192.168.0.3, though a specific queue you could use +specific host, for example 192.168.0.3, through a specific queue you could use this action and establish a filter such as: tc filter add dev eth0 parent 1: protocol ip prio 1 u32 \