List cover comments

GET /api/covers/53828/comments/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Link: 
<http://patches.dpdk.org/api/covers/53828/comments/?format=api&page=1>; rel="first",
<http://patches.dpdk.org/api/covers/53828/comments/?format=api&page=1>; rel="last"
Vary: Accept
[ { "id": 96527, "web_url": "http://patches.dpdk.org/comment/96527/", "msgid": "<CAJFAV8zR8Fjcx0xzkGRFA=euOn9KfKjv04c0NOVZa94A0=wmww@mail.gmail.com>", "list_archive_url": "https://inbox.dpdk.org/dev/CAJFAV8zR8Fjcx0xzkGRFA=euOn9KfKjv04c0NOVZa94A0=wmww@mail.gmail.com", "date": "2019-05-29T20:11:41", "subject": "Re: [dpdk-dev] [PATCH 00/25] Make shared memory config non-public", "submitter": { "id": 1173, "url": "http://patches.dpdk.org/api/people/1173/?format=api", "name": "David Marchand", "email": "david.marchand@redhat.com" }, "content": "On Wed, May 29, 2019 at 6:31 PM Anatoly Burakov <anatoly.burakov@intel.com>\nwrote:\n\n> This patchset removes the shared memory config from public\n> API, and replaces all usages of said config with new API\n> calls.\n>\n> The patchset is mostly a search-and-replace job and should\n> be pretty easy to review. However, the changes to ENA\n>\n\nI went and did the same job with some scripts.\n\nNot sure you really need to split in all those patches.\nWe are not going to backport this.\nSome changes are mixed, the kni changes are in the hash: patch.\n\n\nI spotted a missed qlock in :\nlib/librte_eal/common/eal_common_tailqs.c:\n rte_rwlock_read_lock(&mcfg->qlock);\nlib/librte_eal/common/eal_common_tailqs.c:\n rte_rwlock_read_unlock(&mcfg->qlock);\n\n\nOn the names of the functions, could we have something shorter ?\nThe prefix rte_eal_mcfg_ is not necessary from my pov.\n\n\ndriver are of particular interest, because they're using\n> the shared memory config in a way that i find confusing.\n>\n\nI thought the same when I looked at it before.\nHopefully the ena maintainers will enlight us :-).\n\n\nI tried to implement the equivalent changes as well as\n> i could, but since the code doesn't make any sense to me,\n> i would really like to request help from ENA maintainers.\n>\n> Everything else should be pretty straightforward.\n>\n\nWe are missing the deprecation notice removal at the end of the series and\na note in the release notes.\n\nThanks Anatoly!", "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 2D4C01B944;\n\tWed, 29 May 2019 22:11:55 +0200 (CEST)", "from mail-vs1-f67.google.com (mail-vs1-f67.google.com\n\t[209.85.217.67]) by dpdk.org (Postfix) with ESMTP id 6D6E04F91\n\tfor <dev@dpdk.org>; Wed, 29 May 2019 22:11:53 +0200 (CEST)", "by mail-vs1-f67.google.com with SMTP id m13so77144vsq.12\n\tfor <dev@dpdk.org>; Wed, 29 May 2019 13:11:53 -0700 (PDT)" ], "X-Google-DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed;\n\td=1e100.net; s=20161025;\n\th=x-gm-message-state:mime-version:references:in-reply-to:from:date\n\t:message-id:subject:to:cc;\n\tbh=hGYNmKG1JFImdxn0Gl1j08PNQn10V4BXCk1bRUSHk5w=;\n\tb=D55hTHiEQkjzY/RKw2cfDHvO6+UpxkDB6F0aydjcCOrhLnr2QX01VP3WEfuqQdDsKT\n\tcvbFNvOPcjWH4L78dDsuY0urO8aOpX3T99SCfg1/1XoNTlAvoEGy8o+NfLXmX0y25cyV\n\tc2rgLIC10PfWargGMVPYaV1gV2wqFfKMm383sShyLd+PH+wrIb1Cj00od8rNrlb+tZOD\n\tGV9WMUtDX+Gh8lWCqhPxasEaj9u/TaVQZFRPxsC9A7sIk7vtr2EH5xqDIfn7Qv+keeMX\n\tgfbuM1O06Boa7hTrYjR07Ml1R5aO61+bPtB8aALMHE1dhcXd031T9ButIcz/EGr5DUGL\n\ti6Jg==", "X-Gm-Message-State": "APjAAAUolJfJpDJJc4wiRW6aFaZBbu3kH01qf7+OiJ+MVENo0jAUs278\n\tKGD1KSEATT6kWRQLWhBuipqwB1ClmW2FpqE/lAvd3g==", "X-Google-Smtp-Source": "APXvYqxmltjFB6/IWrr3VQTyrGoinG/dTc520NQRvl3QPL9bQfOJkbaGvDz1Hk5Xq79u99JUUkYGjtRrwpjwP16A53I=", "X-Received": "by 2002:a67:fd85:: with SMTP id k5mr73343413vsq.29.1559160712812;\n\tWed, 29 May 2019 13:11:52 -0700 (PDT)", "MIME-Version": "1.0", "References": "<cover.1559147228.git.anatoly.burakov@intel.com>", "In-Reply-To": "<cover.1559147228.git.anatoly.burakov@intel.com>", "From": "David Marchand <david.marchand@redhat.com>", "Date": "Wed, 29 May 2019 22:11:41 +0200", "Message-ID": "<CAJFAV8zR8Fjcx0xzkGRFA=euOn9KfKjv04c0NOVZa94A0=wmww@mail.gmail.com>", "To": "Anatoly Burakov <anatoly.burakov@intel.com>", "Cc": "dev <dev@dpdk.org>, Stephen Hemminger <stephen@networkplumber.org>, \n\tThomas Monjalon <thomas@monjalon.net>", "Content-Type": "text/plain; charset=\"UTF-8\"", "X-Content-Filtered-By": "Mailman/MimeDel 2.1.15", "Subject": "Re: [dpdk-dev] [PATCH 00/25] Make shared memory config non-public", "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": 96548, "web_url": "http://patches.dpdk.org/comment/96548/", "msgid": "<e5de05b0-d7c9-17a4-6c61-56d3e5fa5d6e@intel.com>", "list_archive_url": "https://inbox.dpdk.org/dev/e5de05b0-d7c9-17a4-6c61-56d3e5fa5d6e@intel.com", "date": "2019-05-30T08:07:44", "subject": "Re: [dpdk-dev] [PATCH 00/25] Make shared memory config non-public", "submitter": { "id": 4, "url": "http://patches.dpdk.org/api/people/4/?format=api", "name": "Anatoly Burakov", "email": "anatoly.burakov@intel.com" }, "content": "On 29-May-19 9:11 PM, David Marchand wrote:\n> On Wed, May 29, 2019 at 6:31 PM Anatoly Burakov <anatoly.burakov@intel.com>\n> wrote:\n> \n>> This patchset removes the shared memory config from public\n>> API, and replaces all usages of said config with new API\n>> calls.\n>>\n>> The patchset is mostly a search-and-replace job and should\n>> be pretty easy to review. However, the changes to ENA\n>>\n> \n> I went and did the same job with some scripts.\n> \n> Not sure you really need to split in all those patches.\n> We are not going to backport this.\n\nThe \"separate commits\" thing is made for the benefit of reviewers, not \nbackporters. In my experience it's much easier to get a maintainer to \nreview a smaller patch than it is to look through a wall of irrelevant \nchanges.\n\nThat said, for trivial changes such as these, maybe this is indeed \nunnecessary.\n\n> Some changes are mixed, the kni changes are in the hash: patch.\n\nOops, will fix, thanks for pointing it out!\n\n> \n> \n> I spotted a missed qlock in :\n> lib/librte_eal/common/eal_common_tailqs.c:\n> rte_rwlock_read_lock(&mcfg->qlock);\n> lib/librte_eal/common/eal_common_tailqs.c:\n> rte_rwlock_read_unlock(&mcfg->qlock);\n> \n> \n> On the names of the functions, could we have something shorter ?\n> The prefix rte_eal_mcfg_ is not necessary from my pov.\n\nI can drop the mcfg, but IMO all of these locking functions should be \nkept under one namespace, and rte_eal_ is too broad.\n\n> \n> \n> driver are of particular interest, because they're using\n>> the shared memory config in a way that i find confusing.\n>>\n> \n> I thought the same when I looked at it before.\n> Hopefully the ena maintainers will enlight us :-).\n> \n> \n> I tried to implement the equivalent changes as well as\n>> i could, but since the code doesn't make any sense to me,\n>> i would really like to request help from ENA maintainers.\n>>\n>> Everything else should be pretty straightforward.\n>>\n> \n> We are missing the deprecation notice removal at the end of the series and\n> a note in the release notes.\n\nWill add. Making into V1 deadline was higher priority :D\n\n> \n> Thanks Anatoly!\n> \n>", "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 5A9021B944;\n\tThu, 30 May 2019 10:07:49 +0200 (CEST)", "from mga06.intel.com (mga06.intel.com [134.134.136.31])\n\tby dpdk.org (Postfix) with ESMTP id D67DA5680\n\tfor <dev@dpdk.org>; Thu, 30 May 2019 10:07:47 +0200 (CEST)", "from fmsmga006.fm.intel.com ([10.253.24.20])\n\tby orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;\n\t30 May 2019 01:07:46 -0700", "from itopinsk-mobl.ccr.corp.intel.com (HELO [10.252.14.83])\n\t([10.252.14.83])\n\tby fmsmga006.fm.intel.com with ESMTP; 30 May 2019 01:07:45 -0700" ], "X-Amp-Result": "SKIPPED(no attachment in message)", "X-Amp-File-Uploaded": "False", "X-ExtLoop1": "1", "To": "David Marchand <david.marchand@redhat.com>", "Cc": "dev <dev@dpdk.org>, Stephen Hemminger <stephen@networkplumber.org>,\n\tThomas Monjalon <thomas@monjalon.net>", "References": "<cover.1559147228.git.anatoly.burakov@intel.com>\n\t<CAJFAV8zR8Fjcx0xzkGRFA=euOn9KfKjv04c0NOVZa94A0=wmww@mail.gmail.com>", "From": "\"Burakov, Anatoly\" <anatoly.burakov@intel.com>", "Message-ID": "<e5de05b0-d7c9-17a4-6c61-56d3e5fa5d6e@intel.com>", "Date": "Thu, 30 May 2019 09:07:44 +0100", "User-Agent": "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101\n\tThunderbird/60.7.0", "MIME-Version": "1.0", "In-Reply-To": "<CAJFAV8zR8Fjcx0xzkGRFA=euOn9KfKjv04c0NOVZa94A0=wmww@mail.gmail.com>", "Content-Type": "text/plain; charset=utf-8; format=flowed", "Content-Language": "en-US", "Content-Transfer-Encoding": "7bit", "Subject": "Re: [dpdk-dev] [PATCH 00/25] Make shared memory config non-public", "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": 96552, "web_url": "http://patches.dpdk.org/comment/96552/", "msgid": "<20190530101555.GB1107@bricha3-MOBL.ger.corp.intel.com>", "list_archive_url": "https://inbox.dpdk.org/dev/20190530101555.GB1107@bricha3-MOBL.ger.corp.intel.com", "date": "2019-05-30T10:15:56", "subject": "Re: [dpdk-dev] [PATCH 00/25] Make shared memory config non-public", "submitter": { "id": 20, "url": "http://patches.dpdk.org/api/people/20/?format=api", "name": "Bruce Richardson", "email": "bruce.richardson@intel.com" }, "content": "On Thu, May 30, 2019 at 09:07:44AM +0100, Burakov, Anatoly wrote:\n> On 29-May-19 9:11 PM, David Marchand wrote:\n> > On Wed, May 29, 2019 at 6:31 PM Anatoly Burakov <anatoly.burakov@intel.com>\n> > wrote:\n> > \n> > > This patchset removes the shared memory config from public\n> > > API, and replaces all usages of said config with new API\n> > > calls.\n> > > \n> > > The patchset is mostly a search-and-replace job and should\n> > > be pretty easy to review. However, the changes to ENA\n> > > \n> > \n> > I went and did the same job with some scripts.\n> > \n> > Not sure you really need to split in all those patches.\n> > We are not going to backport this.\n> \n> The \"separate commits\" thing is made for the benefit of reviewers, not\n> backporters. In my experience it's much easier to get a maintainer to review\n> a smaller patch than it is to look through a wall of irrelevant changes.\n> \n> That said, for trivial changes such as these, maybe this is indeed\n> unnecessary.\n> \n> > Some changes are mixed, the kni changes are in the hash: patch.\n> \n> Oops, will fix, thanks for pointing it out!\n> \n> > \n> > \n> > I spotted a missed qlock in :\n> > lib/librte_eal/common/eal_common_tailqs.c:\n> > rte_rwlock_read_lock(&mcfg->qlock);\n> > lib/librte_eal/common/eal_common_tailqs.c:\n> > rte_rwlock_read_unlock(&mcfg->qlock);\n> > \n> > \n> > On the names of the functions, could we have something shorter ?\n> > The prefix rte_eal_mcfg_ is not necessary from my pov.\n> \n> I can drop the mcfg, but IMO all of these locking functions should be kept\n> under one namespace, and rte_eal_ is too broad.\n> \n\nI think most/all developers are aware that memory is part of eal, so\nrte_mcfg_ prefix (or rte_memcfg) might work.", "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 A20461B94D;\n\tThu, 30 May 2019 12:16:01 +0200 (CEST)", "from mga06.intel.com (mga06.intel.com [134.134.136.31])\n\tby dpdk.org (Postfix) with ESMTP id 5CFB34CA6\n\tfor <dev@dpdk.org>; Thu, 30 May 2019 12:16:00 +0200 (CEST)", "from fmsmga006.fm.intel.com ([10.253.24.20])\n\tby orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;\n\t30 May 2019 03:15:59 -0700", "from bricha3-mobl.ger.corp.intel.com ([10.237.221.64])\n\tby fmsmga006.fm.intel.com with SMTP; 30 May 2019 03:15:56 -0700", "by (sSMTP sendmail emulation); Thu, 30 May 2019 11:15:56 +0100" ], "X-Amp-Result": "UNSCANNABLE", "X-Amp-File-Uploaded": "False", "X-ExtLoop1": "1", "Date": "Thu, 30 May 2019 11:15:56 +0100", "From": "Bruce Richardson <bruce.richardson@intel.com>", "To": "\"Burakov, Anatoly\" <anatoly.burakov@intel.com>", "Cc": "David Marchand <david.marchand@redhat.com>, dev <dev@dpdk.org>,\n\tStephen Hemminger <stephen@networkplumber.org>,\n\tThomas Monjalon <thomas@monjalon.net>", "Message-ID": "<20190530101555.GB1107@bricha3-MOBL.ger.corp.intel.com>", "References": "<cover.1559147228.git.anatoly.burakov@intel.com>\n\t<CAJFAV8zR8Fjcx0xzkGRFA=euOn9KfKjv04c0NOVZa94A0=wmww@mail.gmail.com>\n\t<e5de05b0-d7c9-17a4-6c61-56d3e5fa5d6e@intel.com>", "MIME-Version": "1.0", "Content-Type": "text/plain; charset=us-ascii", "Content-Disposition": "inline", "In-Reply-To": "<e5de05b0-d7c9-17a4-6c61-56d3e5fa5d6e@intel.com>", "User-Agent": "Mutt/1.11.4 (2019-03-13)", "Subject": "Re: [dpdk-dev] [PATCH 00/25] Make shared memory config non-public", "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": 96604, "web_url": "http://patches.dpdk.org/comment/96604/", "msgid": "<7690473.PLrV9C041b@xps>", "list_archive_url": "https://inbox.dpdk.org/dev/7690473.PLrV9C041b@xps", "date": "2019-06-03T09:42:48", "subject": "Re: [dpdk-dev] [PATCH 00/25] Make shared memory config non-public", "submitter": { "id": 685, "url": "http://patches.dpdk.org/api/people/685/?format=api", "name": "Thomas Monjalon", "email": "thomas@monjalon.net" }, "content": "30/05/2019 12:15, Bruce Richardson:\n> On Thu, May 30, 2019 at 09:07:44AM +0100, Burakov, Anatoly wrote:\n> > On 29-May-19 9:11 PM, David Marchand wrote:\n> > > On the names of the functions, could we have something shorter ?\n> > > The prefix rte_eal_mcfg_ is not necessary from my pov.\n> > \n> > I can drop the mcfg, but IMO all of these locking functions should be kept\n> > under one namespace, and rte_eal_ is too broad.\n> \n> I think most/all developers are aware that memory is part of eal, so\n> rte_mcfg_ prefix (or rte_memcfg) might work.\n\nWhy not being explicit with \"rte_mem_config_\",\nsame as the structure?", "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 2A99C2C36;\n\tMon, 3 Jun 2019 11:42:54 +0200 (CEST)", "from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com\n\t[66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 959F428F3\n\tfor <dev@dpdk.org>; Mon, 3 Jun 2019 11:42:52 +0200 (CEST)", "from compute1.internal (compute1.nyi.internal [10.202.2.41])\n\tby mailout.nyi.internal (Postfix) with ESMTP id EE2A822182;\n\tMon, 3 Jun 2019 05:42:51 -0400 (EDT)", "from mailfrontend2 ([10.202.2.163])\n\tby compute1.internal (MEProxy); Mon, 03 Jun 2019 05:42:51 -0400", "from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])\n\tby mail.messagingengine.com (Postfix) with ESMTPA id 71D3A38008C;\n\tMon, 3 Jun 2019 05:42:50 -0400 (EDT)" ], "DKIM-Signature": [ "v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=\n\tfrom:to:cc:subject:date:message-id:in-reply-to:references\n\t:mime-version:content-transfer-encoding:content-type; s=mesmtp;\n\tbh=Tjv2L6Zcvc1eAa0+CD8epevmMnLBqRUMui0Sq7P792s=; b=SQbwNetckpAp\n\tmwiYm9hyLtC3bQGDP/0Tq3vRjq+jTeVZyF8JD1cTkbQEiZsSMN8J5sos4i63ruf1\n\tMk95Hf1AOPv5tqiASkO8nT0xdW7j+Lgqqc34Cw9jcnG4ehM9aopFyFlP7I9x3QF4\n\tr0G/hJa8uOMOx55PVIwSuhq5w7J5Oac=", "v=1; a=rsa-sha256; c=relaxed/relaxed; d=\n\tmessagingengine.com; h=cc:content-transfer-encoding:content-type\n\t:date:from:in-reply-to:message-id:mime-version:references\n\t:subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender\n\t:x-sasl-enc; s=fm2; bh=Tjv2L6Zcvc1eAa0+CD8epevmMnLBqRUMui0Sq7P79\n\t2s=; b=z6NY5atn80DiPcvCEGDPJoG3EDbYob8nAdRPluDnOQaPx5uugSnux5hUv\n\tepRJAcim5znis84hdr4LCAtBsF02yAF43OQEM7r+lJNeLKgikquMXWEnS0ufeLZh\n\t2qpurjrZN1b0GIoFCUssRx153egmBSguAsgfjfQJzoo+dMO9IDfr51l85aD7SSQl\n\tpqbr5s0tNPpoJTk1dAC8DpLX0te4D26Sg19wSMrWkIsbmhZtlZrkGKCT3cHEEf+F\n\tXB2sKzU5CKjSWVlHtIEt//2Y3WMsWwP9vfXRHZL1Whl0b73uOAz98mrbgpgjwFu1\n\tPuiSbtIuZ4j2HLryRODtmSyd0oAlw==" ], "X-ME-Sender": "<xms:m-v0XGRr6psXiZLLOv0IzTjB6GIwKiN0XY5Foc1DtwjI4DUaKbw02w>", "X-ME-Proxy-Cause": "gggruggvucftvghtrhhoucdtuddrgeduuddrudefjedgudeiucetufdoteggodetrfdotf\n\tfvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen\n\tuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne\n\tcujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr\n\tshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf\n\thppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh\n\tohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt", "X-ME-Proxy": "<xmx:m-v0XFIjvNuAouftcO_ne19hzHFbFZUJ51uTBSBqKIefVTSj7KsmxQ>\n\t<xmx:m-v0XM80kVFhzFUAB2nlQNThel0LD6hc_BOUcnl_XyKLXIeyNywHhw>\n\t<xmx:m-v0XFCk9pukQyRifhsI5XXL9tUXTEsRe2qUhN7P01PK6zfhA2nCzw>\n\t<xmx:m-v0XDhUlwgaNet6-M0kiXCGe3aq0oWbbW57SV6Vex6Py8PDrPCsuA>", "From": "Thomas Monjalon <thomas@monjalon.net>", "To": "Bruce Richardson <bruce.richardson@intel.com>, \"Burakov,\n\tAnatoly\" <anatoly.burakov@intel.com>,\n\tDavid Marchand <david.marchand@redhat.com>", "Cc": "dev <dev@dpdk.org>, Stephen Hemminger <stephen@networkplumber.org>", "Date": "Mon, 03 Jun 2019 11:42:48 +0200", "Message-ID": "<7690473.PLrV9C041b@xps>", "In-Reply-To": "<20190530101555.GB1107@bricha3-MOBL.ger.corp.intel.com>", "References": "<cover.1559147228.git.anatoly.burakov@intel.com>\n\t<e5de05b0-d7c9-17a4-6c61-56d3e5fa5d6e@intel.com>\n\t<20190530101555.GB1107@bricha3-MOBL.ger.corp.intel.com>", "MIME-Version": "1.0", "Content-Transfer-Encoding": "7Bit", "Content-Type": "text/plain; charset=\"us-ascii\"", "Subject": "Re: [dpdk-dev] [PATCH 00/25] Make shared memory config non-public", "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 } ]