List comments

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

[
    {
        "id": 83087,
        "web_url": "http://patches.dpdk.org/comment/83087/",
        "msgid": "<cf7b795b-8871-a979-a40a-1a267018025a@intel.com>",
        "date": "2018-07-03T12:33:01",
        "subject": "Re: [dpdk-dev] [PATCH v2 0/6] use IOVAs check based on DMA mask",
        "submitter": {
            "id": 4,
            "url": "http://patches.dpdk.org/api/people/4/",
            "name": "Anatoly Burakov",
            "email": "anatoly.burakov@intel.com"
        },
        "content": "On 03-Jul-18 1:09 PM, Alejandro Lucero wrote:\n> This patchset adds, mainly, a check for ensuring IOVAs are within a\n> restricted range due to addressing limitations with some devices. There\n> are two known cases: NFP and IOMMU VT-d emulation.\n> \n> With this check IOVAs out of range are detected and PMDs can abort\n> initialization. For the VT-d case, IOVA VA mode is allowed as long as\n> IOVAs are within the supported range, avoiding to forbid IOVA VA by\n> default.\n> \n> For the addressing limitations known cases, there are just 40(NFP) or\n> 39(VT-d) bits for handling IOVAs. When using IOVA PA, those limitations\n> imply 1TB(NFP) or 512M(VT-d) as upper limits, which is likely enough for\n> most systems. With machines using more memory, the added check will\n> ensure IOVAs within the range.\n> \n> With IOVA VA, and because the way the Linux kernel serves mmap calls\n> in 64 bits systems, 39 or 40 bits are not enough. It is possible to\n> give an address hint with a lower starting address than the default one\n> used by the kernel, and then ensuring the mmap uses that hint or hint plus\n> some offset. With 64 bits systems, the process virtual address space is\n> large enoguh for doing the hugepages mmaping within the supported range\n> when those addressing limitations exist. This patchset also adds a change\n> for using such a hint making the use of IOVA VA a more than likely\n> possibility when there are those addressing limitations.\n> \n> The check is not done by default but just when it is required. This\n> patchset adds the check for NFP initialization and for setting the IOVA\n> mode is an emulated VT-d is detected.\n> \n> This patchset applies on 17.11.3.\n> \n> Similar changes will be submitted to main DPDK branch soon.\n> \n> v2:\n>   - add get_addr_hint function\n>   - call munmap when hint given and not used by mmap\n>   - create dma mask in one step\n>   - refactor logs\n> \n> \n\nGeneral comment - new API's should probably be added to the .map files?",
        "headers": {
            "Return-Path": "<dev-bounces@dpdk.org>",
            "References": "<1530619789-33337-1-git-send-email-alejandro.lucero@netronome.com>",
            "X-Mailman-Version": "2.1.15",
            "X-IronPort-AV": "E=Sophos;i=\"5.51,303,1526367600\"; d=\"scan'208\";a=\"69282653\"",
            "From": "\"Burakov, Anatoly\" <anatoly.burakov@intel.com>",
            "User-Agent": "Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101\n\tThunderbird/52.8.0",
            "List-Post": "<mailto:dev@dpdk.org>",
            "Content-Type": "text/plain; charset=utf-8; format=flowed",
            "Delivered-To": "patchwork@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 02C281BE98;\n\tTue,  3 Jul 2018 14:33:06 +0200 (CEST)",
                "from mga03.intel.com (mga03.intel.com [134.134.136.65])\n\tby dpdk.org (Postfix) with ESMTP id 644CD1BE46;\n\tTue,  3 Jul 2018 14:33:04 +0200 (CEST)",
                "from fmsmga001.fm.intel.com ([10.253.24.23])\n\tby orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;\n\t03 Jul 2018 05:33:03 -0700",
                "from aburakov-mobl.ger.corp.intel.com (HELO [10.237.220.109])\n\t([10.237.220.109])\n\tby fmsmga001.fm.intel.com with ESMTP; 03 Jul 2018 05:33:01 -0700"
            ],
            "Subject": "Re: [dpdk-dev] [PATCH v2 0/6] use IOVAs check based on DMA mask",
            "Sender": "\"dev\" <dev-bounces@dpdk.org>",
            "X-Amp-File-Uploaded": "False",
            "Content-Language": "en-US",
            "Message-ID": "<cf7b795b-8871-a979-a40a-1a267018025a@intel.com>",
            "Precedence": "list",
            "X-BeenThere": "dev@dpdk.org",
            "Date": "Tue, 3 Jul 2018 13:33:01 +0100",
            "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": "stable@dpdk.org, maxime.coquelin@redhat.com",
            "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
            "In-Reply-To": "<1530619789-33337-1-git-send-email-alejandro.lucero@netronome.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": "7bit",
            "To": "Alejandro Lucero <alejandro.lucero@netronome.com>, dev@dpdk.org",
            "X-Amp-Result": "SKIPPED(no attachment in message)",
            "Errors-To": "dev-bounces@dpdk.org"
        }
    }
]