List comments

GET /api/covers/42819/comments/
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

[
    {
        "id": 83620,
        "web_url": "http://patches.dpdk.org/comment/83620/",
        "msgid": "<20180711084604.61cb5eea@xeon-e3>",
        "date": "2018-07-11T15:46:04",
        "subject": "Re: [dpdk-dev] [PATCH v9 0/7] hotplug failure handle mechanism",
        "submitter": {
            "id": 27,
            "url": "http://patches.dpdk.org/api/people/27/",
            "name": "Stephen Hemminger",
            "email": "stephen@networkplumber.org"
        },
        "content": "On Wed, 11 Jul 2018 18:41:50 +0800\nJeff Guo <jia.guo@intel.com> wrote:\n\n> As we know, hot plug is an importance feature, either use for the datacenter\n> device’s fail-safe, or use for SRIOV Live Migration in SDN/NFV. It could bring\n> the higher flexibility and continuality to the networking services in multiple\n> use cases in industry. So let we see, dpdk as an importance networking\n> framework, what can it help to implement hot plug solution for users.\n> \n> We already have a general device event detect mechanism, failsafe driver,\n> bonding driver and hot plug/unplug api in framework, app could use these to\n> develop their hot plug solution.\n\nI like seeing a better solution to hot plug. But it is worth mentioning\nthat for the Hyper-V netvsc driver this is mostly unnecessary. The Hyper-V\nhost notifies the network driver directly about availability of SRIOV\ndevice, and the netvsc device driver can use that to do its own VF\nmanagement. It doesn't really need (or want) to be using a general\nPCI solution.",
        "headers": {
            "Return-Path": "<dev-bounces@dpdk.org>",
            "References": "<1498711073-42917-1-git-send-email-jia.guo@intel.com>\n\t<1531305717-15504-1-git-send-email-jia.guo@intel.com>",
            "X-Mailman-Version": "2.1.15",
            "From": "Stephen Hemminger <stephen@networkplumber.org>",
            "List-Post": "<mailto:dev@dpdk.org>",
            "Content-Type": "text/plain; charset=UTF-8",
            "X-BeenThere": "dev@dpdk.org",
            "X-Original-To": "patchwork@dpdk.org",
            "X-Google-DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=1e100.net; s=20161025;\n\th=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to\n\t:references:mime-version:content-transfer-encoding;\n\tbh=jaG88JadWKuTR9CMSvar56MoOCXyRoj6gNpxRBo0AsM=;\n\tb=ZAT8DnvYn+AYF7dx4P09Ww+302fnOJzgSKBEHQ3+tDZegH99Ypr1zQKyNoqZgGVBZ1\n\t6SIYmnHo7CEBgkBgZwvaMtrskBE793wMZizd53Au80RsnRbvujTwZdy74lesJCkO+ni1\n\tZbe6YuDKItci982MGOtAwI+Pi4F4j18vTbiKWPTGVmM9WAVyrb9NUGKN2p88+pkcHoTC\n\tdouy+1Sk58eECvYJ4U/Tyr80GxF2B7s1jk+n+HCZ3022ogyaxnUoZpZ5R/Ne9VF/qwDT\n\tlIi/k2t5saJ+u+4V1NBa573OV76G5eGlQDq0EEMzjzl0bTHFP8xU63I5z2o6iaAcb8VR\n\t6UcQ==",
            "Received": [
                "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id A9BB81B432;\n\tWed, 11 Jul 2018 17:46:10 +0200 (CEST)",
                "from mail-pg1-f196.google.com (mail-pg1-f196.google.com\n\t[209.85.215.196]) by dpdk.org (Postfix) with ESMTP id 429A11B432\n\tfor <dev@dpdk.org>; Wed, 11 Jul 2018 17:46:09 +0200 (CEST)",
                "by mail-pg1-f196.google.com with SMTP id n15-v6so3022930pgv.4\n\tfor <dev@dpdk.org>; Wed, 11 Jul 2018 08:46:09 -0700 (PDT)",
                "from xeon-e3 (204-195-22-127.wavecable.com. [204.195.22.127])\n\tby smtp.gmail.com with ESMTPSA id\n\tl25-v6sm4580380pff.8.2018.07.11.08.46.07\n\t(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);\n\tWed, 11 Jul 2018 08:46:08 -0700 (PDT)"
            ],
            "Subject": "Re: [dpdk-dev] [PATCH v9 0/7] hotplug failure handle mechanism",
            "X-Received": "by 2002:a62:2785:: with SMTP id\n\tn127-v6mr30782125pfn.129.1531323968420; \n\tWed, 11 Jul 2018 08:46:08 -0700 (PDT)",
            "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
            "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=networkplumber-org.20150623.gappssmtp.com; s=20150623;\n\th=date:from:to:cc:subject:message-id:in-reply-to:references\n\t:mime-version:content-transfer-encoding;\n\tbh=jaG88JadWKuTR9CMSvar56MoOCXyRoj6gNpxRBo0AsM=;\n\tb=S6xCzeZgSxjqXGWalPqPzVUwSfNRF2l60bG/f02Vr5lUAPC5BvPQAkEJ2TzwOiZuBa\n\tnaQeUXOVyKZjIY4CzCUCLjWfUEe/ZLqSLEQQdjKbsckteV5bBi42/XUV1dN13Nz8xsnV\n\t7jFTT2i/Y3jQpws1zIjYfiqDavp8BjWCP114Sm11VrqMGe+BhAxy/AyQLlsKBZ/Igb8w\n\tUz+7m7TdN7XiCU0+H3KWNIUq8kZahFlQDJ1GAXN3DByDL7SMDMxKnaXmT+JdqPE/62j7\n\tRZuFaKoUEDGQWrxuAlEo0lwpuURO4fHcjqiZWpkKe4X69pF1w8XaOje3F5eV1CT4Lxvv\n\twsUg==",
            "Message-ID": "<20180711084604.61cb5eea@xeon-e3>",
            "Precedence": "list",
            "X-Gm-Message-State": "APt69E18TeVabzIS8PiCrxQd6Hl6UyhHXWdU26RvDMVIk0uSXpWuyH/E\n\tVqVmBfNeIBmyVBgXsKqaExSUYg==",
            "Date": "Wed, 11 Jul 2018 08:46:04 -0700",
            "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
            "Sender": "\"dev\" <dev-bounces@dpdk.org>",
            "Errors-To": "dev-bounces@dpdk.org",
            "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>",
            "X-Google-Smtp-Source": "AAOMgpf2g62Xbbc8peqny11Ku2Tni2WBRKqB/LjOuZufW1K3gweJHP7QHXnv5Ou+mw76IY80AywphQ==",
            "Cc": "bruce.richardson@intel.com, ferruh.yigit@intel.com,\n\tkonstantin.ananyev@intel.com, gaetan.rivet@6wind.com,\n\tjingjing.wu@intel.com, thomas@monjalon.net, motih@mellanox.com,\n\tmatan@mellanox.com, harry.van.haaren@intel.com, qi.z.zhang@intel.com, \n\tshaopeng.he@intel.com, bernard.iremonger@intel.com,\n\tarybchenko@solarflare.com, wenzhuo.lu@intel.com, jblunck@infradead.org,\n\tshreyansh.jain@nxp.com, dev@dpdk.org, helin.zhang@intel.com",
            "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
            "Delivered-To": "patchwork@dpdk.org",
            "In-Reply-To": "<1531305717-15504-1-git-send-email-jia.guo@intel.com>",
            "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>",
            "MIME-Version": "1.0",
            "Content-Transfer-Encoding": "quoted-printable",
            "To": "Jeff Guo <jia.guo@intel.com>"
        }
    },
    {
        "id": 83658,
        "web_url": "http://patches.dpdk.org/comment/83658/",
        "msgid": "<f3ee819e-1dbe-9970-3426-9d21224557f2@intel.com>",
        "date": "2018-07-12T03:14:28",
        "subject": "Re: [dpdk-dev] [PATCH v9 0/7] hotplug failure handle mechanism",
        "submitter": {
            "id": 507,
            "url": "http://patches.dpdk.org/api/people/507/",
            "name": "Guo, Jia",
            "email": "jia.guo@intel.com"
        },
        "content": "On 7/11/2018 11:46 PM, Stephen Hemminger wrote:\n> On Wed, 11 Jul 2018 18:41:50 +0800\n> Jeff Guo <jia.guo@intel.com> wrote:\n>\n>> As we know, hot plug is an importance feature, either use for the datacenter\n>> device’s fail-safe, or use for SRIOV Live Migration in SDN/NFV. It could bring\n>> the higher flexibility and continuality to the networking services in multiple\n>> use cases in industry. So let we see, dpdk as an importance networking\n>> framework, what can it help to implement hot plug solution for users.\n>>\n>> We already have a general device event detect mechanism, failsafe driver,\n>> bonding driver and hot plug/unplug api in framework, app could use these to\n>> develop their hot plug solution.\n> I like seeing a better solution to hot plug. But it is worth mentioning\n> that for the Hyper-V netvsc driver this is mostly unnecessary. The Hyper-V\n> host notifies the network driver directly about availability of SRIOV\n> device, and the netvsc device driver can use that to do its own VF\n> management. It doesn't really need (or want) to be using a general\n> PCI solution.\n\nI am not sure about Hyper-v netvsc driver, but i am very interesting to \ndeep analyze it to find what could let we find a best solution for \nhotplug. But since some customer, who like me still not have chance to \nuse Hyper-v, they will encounter the hotplug issue when use kvm or other \nplatform.\nso  let we said that the topic about here is aim to fix the issue for \nthat part of customer or developer.  Just let hotplug be used more in \ndiversity scenario.",
        "headers": {
            "Return-Path": "<dev-bounces@dpdk.org>",
            "References": "<1498711073-42917-1-git-send-email-jia.guo@intel.com>\n\t<1531305717-15504-1-git-send-email-jia.guo@intel.com>\n\t<20180711084604.61cb5eea@xeon-e3>",
            "X-Mailman-Version": "2.1.15",
            "X-IronPort-AV": "E=Sophos;i=\"5.51,341,1526367600\"; d=\"scan'208\";a=\"239675910\"",
            "From": "Jeff Guo <jia.guo@intel.com>",
            "User-Agent": "Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101\n\tThunderbird/45.4.0",
            "List-Post": "<mailto:dev@dpdk.org>",
            "Content-Type": "text/plain; charset=utf-8; format=flowed",
            "X-BeenThere": "dev@dpdk.org",
            "X-Original-To": "patchwork@dpdk.org",
            "Received": [
                "from [92.243.14.124] (localhost [127.0.0.1])\n\tby dpdk.org (Postfix) with ESMTP id 12C221B532;\n\tThu, 12 Jul 2018 05:14:42 +0200 (CEST)",
                "from mga07.intel.com (mga07.intel.com [134.134.136.100])\n\tby dpdk.org (Postfix) with ESMTP id 6C2D21B526\n\tfor <dev@dpdk.org>; Thu, 12 Jul 2018 05:14:39 +0200 (CEST)",
                "from orsmga005.jf.intel.com ([10.7.209.41])\n\tby orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;\n\t11 Jul 2018 20:14:36 -0700",
                "from jguo15x-mobl3.ccr.corp.intel.com (HELO [10.67.68.64])\n\t([10.67.68.64])\n\tby orsmga005.jf.intel.com with ESMTP; 11 Jul 2018 20:14:32 -0700"
            ],
            "Subject": "Re: [dpdk-dev] [PATCH v9 0/7] hotplug failure handle mechanism",
            "Sender": "\"dev\" <dev-bounces@dpdk.org>",
            "X-Amp-File-Uploaded": "False",
            "Message-ID": "<f3ee819e-1dbe-9970-3426-9d21224557f2@intel.com>",
            "Precedence": "list",
            "Date": "Thu, 12 Jul 2018 11:14:28 +0800",
            "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
            "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
            "X-ExtLoop1": "1",
            "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n\t<mailto:dev-request@dpdk.org?subject=subscribe>",
            "Cc": "bruce.richardson@intel.com, ferruh.yigit@intel.com,\n\tkonstantin.ananyev@intel.com, gaetan.rivet@6wind.com,\n\tjingjing.wu@intel.com, \n\tthomas@monjalon.net, motih@mellanox.com, matan@mellanox.com,\n\tharry.van.haaren@intel.com, qi.z.zhang@intel.com, shaopeng.he@intel.com, \n\tbernard.iremonger@intel.com, arybchenko@solarflare.com,\n\twenzhuo.lu@intel.com, jblunck@infradead.org, shreyansh.jain@nxp.com, \n\tdev@dpdk.org, helin.zhang@intel.com",
            "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
            "Delivered-To": "patchwork@dpdk.org",
            "In-Reply-To": "<20180711084604.61cb5eea@xeon-e3>",
            "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n\t<mailto:dev-request@dpdk.org?subject=unsubscribe>",
            "MIME-Version": "1.0",
            "Content-Transfer-Encoding": "8bit",
            "To": "Stephen Hemminger <stephen@networkplumber.org>",
            "X-Amp-Result": "SKIPPED(no attachment in message)",
            "Errors-To": "dev-bounces@dpdk.org"
        }
    }
]