From patchwork Tue Dec 20 02:34:15 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: solomon X-Patchwork-Id: 132343 X-Patchwork-Delegate: davem@davemloft.net Return-Path: X-Original-To: patchwork-incoming@ozlabs.org Delivered-To: patchwork-incoming@ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 9DA83B6FB9 for ; Tue, 20 Dec 2011 13:32:03 +1100 (EST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753435Ab1LTCb7 (ORCPT ); Mon, 19 Dec 2011 21:31:59 -0500 Received: from mail-iy0-f174.google.com ([209.85.210.174]:46359 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751159Ab1LTCb5 (ORCPT ); Mon, 19 Dec 2011 21:31:57 -0500 Received: by iaeh11 with SMTP id h11so9483448iae.19 for ; Mon, 19 Dec 2011 18:31:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type:content-transfer-encoding; bh=OzSZCimLDeZTC5Uxem1VRN1DSwjviWPt3BwtNQZBAMM=; b=XmUk0HkNzByAFItHlcj78t/riqCLXIIfMOInU072n3PfkJ8axxPFscTVLaydwv1L0f KSF38+Tq6R1TbLW4UyRyz2rGn2nHvEAbKaJwSaxq2GxFVrAGLnei3BA15JfLSAWwe76s eybakuQJa+Wd6nXUprnLjjtGUXCe1rkfWTxxo= Received: by 10.50.106.226 with SMTP id gx2mr390629igb.13.1324348317488; Mon, 19 Dec 2011 18:31:57 -0800 (PST) Received: from [127.0.0.1] ([121.14.96.125]) by mx.google.com with ESMTPS id j3sm652139ibj.1.2011.12.19.18.31.54 (version=SSLv3 cipher=OTHER); Mon, 19 Dec 2011 18:31:56 -0800 (PST) Message-ID: <4EEFF427.1090801@gmail.com> Date: Tue, 20 Dec 2011 10:34:15 +0800 From: Shan Wei User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: David Miller CC: =?UTF-8?B?5Y2V5Y2r?= , NetDev Subject: [PATCH net-next ] net: doc: fix many typos in scaling.txt Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Fix some trivial typos. Signed-off-by: Shan Wei --- Documentation/networking/scaling.txt | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/networking/scaling.txt b/Documentation/networking/scaling.txt index a177de2..579994a 100644 --- a/Documentation/networking/scaling.txt +++ b/Documentation/networking/scaling.txt @@ -208,7 +208,7 @@ The counter in rps_dev_flow_table values records the length of the current CPU's backlog when a packet in this flow was last enqueued. Each backlog queue has a head counter that is incremented on dequeue. A tail counter is computed as head counter + queue length. In other words, the counter -in rps_dev_flow_table[i] records the last element in flow i that has +in rps_dev_flow[i] records the last element in flow i that has been enqueued onto the currently designated CPU for flow i (of course, entry i is actually selected by hash and multiple flows may hash to the same entry i). @@ -224,7 +224,7 @@ following is true: - The current CPU's queue head counter >= the recorded tail counter value in rps_dev_flow[i] -- The current CPU is unset (equal to NR_CPUS) +- The current CPU is unset (equal to RPS_NO_CPU) - The current CPU is offline After this check, the packet is sent to the (possibly updated) current @@ -235,7 +235,7 @@ CPU. ==== RFS Configuration -RFS is only available if the kconfig symbol CONFIG_RFS is enabled (on +RFS is only available if the kconfig symbol CONFIG_RPS is enabled (on by default for SMP). The functionality remains disabled until explicitly configured. The number of entries in the global flow table is set through: @@ -258,7 +258,7 @@ For a single queue device, the rps_flow_cnt value for the single queue would normally be configured to the same value as rps_sock_flow_entries. For a multi-queue device, the rps_flow_cnt for each queue might be configured as rps_sock_flow_entries / N, where N is the number of -queues. So for instance, if rps_flow_entries is set to 32768 and there +queues. So for instance, if rps_sock_flow_entries is set to 32768 and there are 16 configured receive queues, rps_flow_cnt for each queue might be configured as 2048.