Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/patches/7323/?format=api
{ "id": 7323, "url": "https://patches.dpdk.org/api/patches/7323/?format=api", "web_url": "https://patches.dpdk.org/project/dpdk/patch/1443621905-7872-10-git-send-email-tomaszx.kulasek@intel.com/", "project": { "id": 1, "url": "https://patches.dpdk.org/api/projects/1/?format=api", "name": "DPDK", "link_name": "dpdk", "list_id": "dev.dpdk.org", "list_email": "dev@dpdk.org", "web_url": "http://core.dpdk.org", "scm_url": "git://dpdk.org/dpdk", "webscm_url": "http://git.dpdk.org/dpdk", "list_archive_url": "https://inbox.dpdk.org/dev", "list_archive_url_format": "https://inbox.dpdk.org/dev/{}", "commit_url_format": "" }, "msgid": "<1443621905-7872-10-git-send-email-tomaszx.kulasek@intel.com>", "list_archive_url": "https://inbox.dpdk.org/dev/1443621905-7872-10-git-send-email-tomaszx.kulasek@intel.com", "date": "2015-09-30T14:05:05", "name": "[dpdk-dev,v5,9/9] doc: dynamic rss configuration for bonding", "commit_ref": null, "pull_url": null, "state": "superseded", "archived": true, "hash": "d5cacb454a11da8b2f2ea8ca1ca3eb1778045822", "submitter": { "id": 155, "url": "https://patches.dpdk.org/api/people/155/?format=api", "name": "Tomasz Kulasek", "email": "tomaszx.kulasek@intel.com" }, "delegate": null, "mbox": "https://patches.dpdk.org/project/dpdk/patch/1443621905-7872-10-git-send-email-tomaszx.kulasek@intel.com/mbox/", "series": [], "comments": "https://patches.dpdk.org/api/patches/7323/comments/", "check": "pending", "checks": "https://patches.dpdk.org/api/patches/7323/checks/", "tags": {}, "related": [], "headers": { "Return-Path": "<dev-bounces@dpdk.org>", "X-Original-To": "patchwork@dpdk.org", "Delivered-To": "patchwork@dpdk.org", "Received": [ "from [92.243.14.124] (localhost [IPv6:::1])\n\tby dpdk.org (Postfix) with ESMTP id DCA7D8DB5;\n\tWed, 30 Sep 2015 16:19:56 +0200 (CEST)", "from mga01.intel.com (mga01.intel.com [192.55.52.88])\n\tby dpdk.org (Postfix) with ESMTP id 186848D91\n\tfor <dev@dpdk.org>; Wed, 30 Sep 2015 16:19:55 +0200 (CEST)", "from orsmga001.jf.intel.com ([10.7.209.18])\n\tby fmsmga101.fm.intel.com with ESMTP; 30 Sep 2015 07:19:39 -0700", "from unknown (HELO Sent) ([10.217.248.94])\n\tby orsmga001.jf.intel.com with SMTP; 30 Sep 2015 07:19:38 -0700", "by Sent (sSMTP sendmail emulation); Wed, 30 Sep 2015 16:18:13 +0200" ], "X-ExtLoop1": "1", "X-IronPort-AV": "E=Sophos;i=\"5.17,612,1437462000\"; d=\"scan'208\";a=\"780954239\"", "From": "Tomasz Kulasek <tomaszx.kulasek@intel.com>", "To": "dev@dpdk.org", "Date": "Wed, 30 Sep 2015 16:05:05 +0200", "Message-Id": "<1443621905-7872-10-git-send-email-tomaszx.kulasek@intel.com>", "X-Mailer": "git-send-email 2.1.4", "In-Reply-To": "<1443621905-7872-1-git-send-email-tomaszx.kulasek@intel.com>", "References": "<1436981189-3320-1-git-send-email-tomaszx.kulasek@intel.com>\n\t<1443621905-7872-1-git-send-email-tomaszx.kulasek@intel.com>", "Subject": "[dpdk-dev] [PATCH v5 9/9] doc: dynamic rss configuration for bonding", "X-BeenThere": "dev@dpdk.org", "X-Mailman-Version": "2.1.15", "Precedence": "list", "List-Id": "patches and discussions about DPDK <dev.dpdk.org>", "List-Unsubscribe": "<http://dpdk.org/ml/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>", "List-Archive": "<http://dpdk.org/ml/archives/dev/>", "List-Post": "<mailto:dev@dpdk.org>", "List-Help": "<mailto:dev-request@dpdk.org?subject=help>", "List-Subscribe": "<http://dpdk.org/ml/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>", "Errors-To": "dev-bounces@dpdk.org", "Sender": "\"dev\" <dev-bounces@dpdk.org>" }, "content": "Documentation update about implementation details and requirements for\nDynamic RSS Configuration for Bonding.\n\nSigned-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com>\n---\n .../prog_guide/link_bonding_poll_mode_drv_lib.rst | 34 ++++++++++++++++++--\n 1 file changed, 32 insertions(+), 2 deletions(-)", "diff": "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\nindex 03baf90..46f0296 100644\n--- a/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst\n+++ b/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst\n@@ -1,5 +1,5 @@\n .. BSD LICENSE\n- Copyright(c) 2010-2014 Intel Corporation. All rights reserved.\n+ Copyright(c) 2010-2015 Intel Corporation. All rights reserved.\n All rights reserved.\n \n Redistribution and use in source and binary forms, with or without\n@@ -173,7 +173,28 @@ After a slave device is added to a bonded device slave is stopped using\n ``rte_eth_dev_stop`` and then reconfigured using ``rte_eth_dev_configure``\n the RX and TX queues are also reconfigured using ``rte_eth_tx_queue_setup`` /\n ``rte_eth_rx_queue_setup`` with the parameters use to configure the bonding\n-device.\n+device. If RSS is enabled for bonding device, this mode is also enabled on new\n+slave and configured as well.\n+\n+Setting up multi-queue mode for bonding device to RSS, makes it fully\n+RSS-capable, so all slaves are synchronized with its configuration. This mode is\n+intended to provide RSS configuration on slaves transparent for client\n+application implementation.\n+\n+Bonding device stores its own version of RSS settings i.e. RETA, RSS hash\n+function and RSS key, used to set up its slaves. That let to define the meaning\n+of RSS configuration of bonding device as desired configuration of whole bonding\n+(as one unit), without pointing any of slave inside. It is required to ensure\n+consistency and made it more errorproof.\n+\n+RSS hash function set for bonding device, is a maximal set of RSS hash functions\n+supported by all bonded slaves. RETA size is a GCD of all its RETA's sizes, so\n+it can be easily used as a pattern providing expected behavior, even if slave\n+RETAs' sizes are different. If RSS Key is not set for bonded device, it's not\n+changed on the slaves and default key for device is used.\n+\n+All settings are managed through the bonding port API and always are propagated\n+in one direction (from bonding to slaves).\n \n Link Status Change Interrupts / Polling\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n@@ -207,6 +228,15 @@ these parameters.\n A bonding device must have a minimum of one slave before the bonding device\n itself can be started.\n \n+To use a bonding device dynamic RSS configuration feature effectively, it is\n+also required, that all slaves should be RSS-capable and support, at least one\n+common hash function available for each of them. Changing RSS key is only\n+possible, when all slave devices support the same key size.\n+\n+To prevent inconsistency on how slaves process packets, once a device is added\n+to a bonding device, RSS configuration should be managed through the bonding\n+device API, and not directly on the slave.\n+\n Like all other PMD, all functions exported by a PMD are lock-free functions\n that are assumed not to be invoked in parallel on different logical cores to\n work on the same target object.\n", "prefixes": [ "dpdk-dev", "v5", "9/9" ] }