Cover Comment List
List cover comments
GET /api/covers/41487/comments/?format=api
[ { "id": 84735, "web_url": "http://patches.dpdk.org/comment/84735/", "msgid": "<b7d24619-6bcf-c4b0-8a8e-388606b72a6f@intel.com>", "list_archive_url": "https://inbox.dpdk.org/dev/b7d24619-6bcf-c4b0-8a8e-388606b72a6f@intel.com", "date": "2018-08-14T10:11:45", "subject": "Re: [dpdk-dev] [RFC 0/9] Modularize and enhance DPDK Python scripts", "submitter": { "id": 4, "url": "http://patches.dpdk.org/api/people/4/?format=api", "name": "Anatoly Burakov", "email": "anatoly.burakov@intel.com" }, "content": "On 25-Jun-18 4:59 PM, Anatoly Burakov wrote:\n> This patchset attempts to create a library out of Python scripts that\n> come with DPDK, with a goal of enabling external tools to get the same\n> information about the system DPDK has, and perhaps configure DPDK.\n> \n> Potential applications include:\n> \n> * Better setup.sh script (it's long overdue, and you know it!)\n> * Easier development of better tools for developers (see hugepage-info\n> example)\n> * Easier gathering of DPDK-centric system information, has potential\n> applications in troubleshooting tools\n> * Reduce code duplication for external tools seeking to use the same\n> functionality (bind-unbind, cpu layout, etc)\n> * Add cross-platform support for our scripts (see cpu-layout example\n> now working on FreeBSD)\n> \n> There are a few things to mention. First of all, it's an RFC, so the\n> fact that it's unfinished and maybe awkward comes with the territory.\n> I am also aware of the fact that it's a Python library, that it's\n> outside the scope of DPDK and that it's somewhat a Not-Invented-Here\n> kind of proposition where there are a lot of externally available\n> (and arguably much better designed and implemented) tools that do the\n> same thing.\n> \n> So the first question i would like to ask is, is the community at all\n> interested in something like this? Does it have to be part of DPDK\n> repository? Can it be maintained in a separate repository? How do we\n> handle updates and dependencies?\n> \n> I should also mention that it is *not* intended to be a replacement\n> for udev or any other method of device binding - if anything, it's\n> the opposite, in that it takes the whole issue out of the question\n> and thus would make switching to udev or any other device binding\n> easier since both internal and external tools can utilize the same\n> Python API.\n> \n\nI would like to draw attention to this RFC again :)", "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 [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id 1EE7E4C8B;\n\tTue, 14 Aug 2018 12:11:56 +0200 (CEST)", "from mga12.intel.com (mga12.intel.com [192.55.52.136])\n\tby dpdk.org (Postfix) with ESMTP id BB1AA4C88\n\tfor <dev@dpdk.org>; Tue, 14 Aug 2018 12:11:54 +0200 (CEST)", "from orsmga002.jf.intel.com ([10.7.209.21])\n\tby fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;\n\t14 Aug 2018 03:11:53 -0700", "from miacopin-mobl1.ger.corp.intel.com (HELO [10.252.22.171])\n\t([10.252.22.171])\n\tby orsmga002.jf.intel.com with ESMTP; 14 Aug 2018 03:11:49 -0700" ], "X-Amp-Result": "SKIPPED(no attachment in message)", "X-Amp-File-Uploaded": "False", "X-ExtLoop1": "1", "X-IronPort-AV": "E=Sophos;i=\"5.53,237,1531810800\"; d=\"scan'208\";a=\"83231992\"", "To": "dev@dpdk.org", "Cc": "john.mcnamara@intel.com, bruce.richardson@intel.com,\n\tpablo.de.lara.guarch@intel.com, david.hunt@intel.com,\n\tmohammad.abdul.awal@intel.com", "References": "<cover.1529940601.git.anatoly.burakov@intel.com>", "From": "\"Burakov, Anatoly\" <anatoly.burakov@intel.com>", "Message-ID": "<b7d24619-6bcf-c4b0-8a8e-388606b72a6f@intel.com>", "Date": "Tue, 14 Aug 2018 11:11:45 +0100", "User-Agent": "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101\n\tThunderbird/52.9.1", "MIME-Version": "1.0", "In-Reply-To": "<cover.1529940601.git.anatoly.burakov@intel.com>", "Content-Type": "text/plain; charset=utf-8; format=flowed", "Content-Language": "en-US", "Content-Transfer-Encoding": "7bit", "Subject": "Re: [dpdk-dev] [RFC 0/9] Modularize and enhance DPDK Python scripts", "X-BeenThere": "dev@dpdk.org", "X-Mailman-Version": "2.1.15", "Precedence": "list", "List-Id": "DPDK patches and discussions <dev.dpdk.org>", "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>", "List-Archive": "<http://mails.dpdk.org/archives/dev/>", "List-Post": "<mailto:dev@dpdk.org>", "List-Help": "<mailto:dev-request@dpdk.org?subject=help>", "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>", "Errors-To": "dev-bounces@dpdk.org", "Sender": "\"dev\" <dev-bounces@dpdk.org>" }, "addressed": null }, { "id": 84997, "web_url": "http://patches.dpdk.org/comment/84997/", "msgid": "<9c694099-07f7-d805-9b23-1c06b0eef128@intel.com>", "list_archive_url": "https://inbox.dpdk.org/dev/9c694099-07f7-d805-9b23-1c06b0eef128@intel.com", "date": "2018-08-28T08:16:59", "subject": "Re: [dpdk-dev] [RFC 0/9] Modularize and enhance DPDK Python scripts", "submitter": { "id": 4, "url": "http://patches.dpdk.org/api/people/4/?format=api", "name": "Anatoly Burakov", "email": "anatoly.burakov@intel.com" }, "content": "On 14-Aug-18 11:11 AM, Burakov, Anatoly wrote:\n> On 25-Jun-18 4:59 PM, Anatoly Burakov wrote:\n>> This patchset attempts to create a library out of Python scripts that\n>> come with DPDK, with a goal of enabling external tools to get the same\n>> information about the system DPDK has, and perhaps configure DPDK.\n>>\n>> Potential applications include:\n>>\n>> * Better setup.sh script (it's long overdue, and you know it!)\n>> * Easier development of better tools for developers (see hugepage-info\n>> example)\n>> * Easier gathering of DPDK-centric system information, has potential\n>> applications in troubleshooting tools\n>> * Reduce code duplication for external tools seeking to use the same\n>> functionality (bind-unbind, cpu layout, etc)\n>> * Add cross-platform support for our scripts (see cpu-layout example\n>> now working on FreeBSD)\n>>\n>> There are a few things to mention. First of all, it's an RFC, so the\n>> fact that it's unfinished and maybe awkward comes with the territory.\n>> I am also aware of the fact that it's a Python library, that it's\n>> outside the scope of DPDK and that it's somewhat a Not-Invented-Here\n>> kind of proposition where there are a lot of externally available\n>> (and arguably much better designed and implemented) tools that do the\n>> same thing.\n>>\n>> So the first question i would like to ask is, is the community at all\n>> interested in something like this? Does it have to be part of DPDK\n>> repository? Can it be maintained in a separate repository? How do we\n>> handle updates and dependencies?\n>>\n>> I should also mention that it is *not* intended to be a replacement\n>> for udev or any other method of device binding - if anything, it's\n>> the opposite, in that it takes the whole issue out of the question\n>> and thus would make switching to udev or any other device binding\n>> easier since both internal and external tools can utilize the same\n>> Python API.\n>>\n> \n> I would like to draw attention to this RFC again :)\n> \n\nPing?", "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 [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id 0E0612BB1;\n\tTue, 28 Aug 2018 10:17:05 +0200 (CEST)", "from mga04.intel.com (mga04.intel.com [192.55.52.120])\n\tby dpdk.org (Postfix) with ESMTP id AF82EDED\n\tfor <dev@dpdk.org>; Tue, 28 Aug 2018 10:17:02 +0200 (CEST)", "from orsmga006.jf.intel.com ([10.7.209.51])\n\tby fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;\n\t28 Aug 2018 01:17:01 -0700", "from soeby-mobl.ger.corp.intel.com (HELO [10.252.19.107])\n\t([10.252.19.107])\n\tby orsmga006.jf.intel.com with ESMTP; 28 Aug 2018 01:17:00 -0700" ], "X-Amp-Result": "SKIPPED(no attachment in message)", "X-Amp-File-Uploaded": "False", "X-ExtLoop1": "1", "X-IronPort-AV": "E=Sophos;i=\"5.53,298,1531810800\"; d=\"scan'208\";a=\"69673415\"", "To": "dev@dpdk.org", "Cc": "john.mcnamara@intel.com, bruce.richardson@intel.com,\n\tpablo.de.lara.guarch@intel.com, david.hunt@intel.com,\n\tmohammad.abdul.awal@intel.com", "References": "<cover.1529940601.git.anatoly.burakov@intel.com>\n\t<b7d24619-6bcf-c4b0-8a8e-388606b72a6f@intel.com>", "From": "\"Burakov, Anatoly\" <anatoly.burakov@intel.com>", "Message-ID": "<9c694099-07f7-d805-9b23-1c06b0eef128@intel.com>", "Date": "Tue, 28 Aug 2018 09:16:59 +0100", "User-Agent": "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101\n\tThunderbird/52.9.1", "MIME-Version": "1.0", "In-Reply-To": "<b7d24619-6bcf-c4b0-8a8e-388606b72a6f@intel.com>", "Content-Type": "text/plain; charset=utf-8; format=flowed", "Content-Language": "en-US", "Content-Transfer-Encoding": "8bit", "Subject": "Re: [dpdk-dev] [RFC 0/9] Modularize and enhance DPDK Python scripts", "X-BeenThere": "dev@dpdk.org", "X-Mailman-Version": "2.1.15", "Precedence": "list", "List-Id": "DPDK patches and discussions <dev.dpdk.org>", "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>", "List-Archive": "<http://mails.dpdk.org/archives/dev/>", "List-Post": "<mailto:dev@dpdk.org>", "List-Help": "<mailto:dev-request@dpdk.org?subject=help>", "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>", "Errors-To": "dev-bounces@dpdk.org", "Sender": "\"dev\" <dev-bounces@dpdk.org>" }, "addressed": null } ]