From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id DDD345927 for ; Fri, 16 Oct 2015 12:14:02 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP; 16 Oct 2015 03:14:01 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,688,1437462000"; d="scan'208";a="828141676" Received: from unknown (HELO Sent) ([10.217.248.129]) by orsmga002.jf.intel.com with SMTP; 16 Oct 2015 03:14:01 -0700 Received: by Sent (sSMTP sendmail emulation); Fri, 16 Oct 2015 12:12:35 +0200 From: Tomasz Kulasek To: dev@dpdk.org Date: Fri, 16 Oct 2015 12:00:50 +0200 Message-Id: <1444989651-6236-9-git-send-email-tomaszx.kulasek@intel.com> X-Mailer: git-send-email 2.1.4 In-Reply-To: <1444989651-6236-1-git-send-email-tomaszx.kulasek@intel.com> References: <1443621905-7872-1-git-send-email-tomaszx.kulasek@intel.com> <1444989651-6236-1-git-send-email-tomaszx.kulasek@intel.com> Subject: [dpdk-dev] [PATCH v6 8/9] doc: fixed spellings and typos X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2015 10:14:03 -0000 Signed-off-by: Tomasz Kulasek --- .../prog_guide/link_bonding_poll_mode_drv_lib.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst b/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst index 96e554f..03baf90 100644 --- a/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst +++ b/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst @@ -188,7 +188,7 @@ conditions are not met. If a user wishes to monitor individual slaves then they must register callbacks with that slave directly. The link bonding library also supports devices which do not implement link -status change interrupts, this is achieve by polling the devices link status at +status change interrupts, this is achieved by polling the devices link status at a defined period which is set using the ``rte_eth_bond_link_monitoring_set`` API, the default polling interval is 10ms. When a device is added as a slave to a bonding device it is determined using the ``RTE_PCI_DRV_INTR_LSC`` flag @@ -286,7 +286,7 @@ and UDP protocols for load balancing. Using Link Bonding Devices -------------------------- -The librte_pmd_bond library support two modes of device creation, the libraries +The librte_pmd_bond library supports two modes of device creation, the libraries export full C API or using the EAL command line to statically configure link bonding devices at application startup. Using the EAL option it is possible to use link bonding functionality transparently without specific knowledge of the @@ -299,7 +299,7 @@ Using the Poll Mode Driver from an Application Using the librte_pmd_bond libraries API it is possible to dynamically create and manage link bonding device from within any application. Link bonding -device are created using the ``rte_eth_bond_create`` API which requires a +devices are created using the ``rte_eth_bond_create`` API which requires a unique device name, the link bonding mode to initial the device in and finally the socket Id which to allocate the devices resources onto. After successful creation of a bonding device it must be configured using the generic Ethernet @@ -362,7 +362,7 @@ The different options are: mode=2 * slave: Defines the PMD device which will be added as slave to the bonded - device. This option can be selected multiple time, for each device to be + device. This option can be selected multiple times, for each device to be added as a slave. Physical devices should be specified using their PCI address, in the format domain:bus:devid.function -- 1.7.9.5