From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <p.fedin@samsung.com> Received: from mailout3.w1.samsung.com (mailout3.w1.samsung.com [210.118.77.13]) by dpdk.org (Postfix) with ESMTP id 565FC8DAF for <dev@dpdk.org>; Wed, 13 Jan 2016 10:40:20 +0100 (CET) Received: from eucpsbgm1.samsung.com (unknown [203.254.199.244]) by mailout3.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0O0V00IYJXJ6F940@mailout3.w1.samsung.com> for dev@dpdk.org; Wed, 13 Jan 2016 09:40:18 +0000 (GMT) X-AuditID: cbfec7f4-f79026d00000418a-00-56961b82366d Received: from eusync3.samsung.com ( [203.254.199.213]) by eucpsbgm1.samsung.com (EUCPMTA) with SMTP id 63.36.16778.28B16965; Wed, 13 Jan 2016 09:40:18 +0000 (GMT) Received: from fedinw7x64 ([106.109.131.169]) by eusync3.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTPA id <0O0V00AGJXJ5IH50@eusync3.samsung.com>; Wed, 13 Jan 2016 09:40:18 +0000 (GMT) From: Pavel Fedin <p.fedin@samsung.com> To: "'Xie, Huawei'" <huawei.xie@intel.com>, dev@dpdk.org References: <005a01d14dd4$a02c5340$e084f9c0$@samsung.com> <C37D651A908B024F974696C65296B57B4C5827EE@SHSMSX101.ccr.corp.intel.com> In-reply-to: <C37D651A908B024F974696C65296B57B4C5827EE@SHSMSX101.ccr.corp.intel.com> Date: Wed, 13 Jan 2016 12:40:17 +0300 Message-id: <006a01d14de6$69c68610$3d539230$@samsung.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-index: AQJ7ONd2zR/jO0iuVPToYLH0pUpzZAICOqktnZVIaNA= Content-language: ru X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHLMWRmVeSWpSXmKPExsVy+t/xq7pN0tPCDBbtl7F492k7k0X7zLNM DkwevxYsZfVYvOclUwBTFJdNSmpOZllqkb5dAlfGi+19TAUHmCte9C1ma2D8yNTFyMkhIWAi sXjjGihbTOLCvfVsXYxcHEICSxklJix6zQLhfGeU+Nq9DqyKTUBd4vTXDywgtoiAhcThFx3M EEXNjBIHmx+ygiQ4BcIkLm+dBVYkLFAtMfnjKkYQm0VAVeLb75tsIDavgKVE47V2dghbUOLH 5Htg9cwCWhLrdx5ngrDlJTavecsMcZ6CxI6zrxkhFltJ7Hq/mh2iRkRi2r97zBMYBWchGTUL yahZSEbNQtKygJFlFaNoamlyQXFSeq6hXnFibnFpXrpecn7uJkZIKH/Zwbj4mNUhRgEORiUe 3o5ZU8OEWBPLiitzDzFKcDArifB6SE0LE+JNSaysSi3Kjy8qzUktPsQozcGiJM47d9f7ECGB 9MSS1OzU1ILUIpgsEwenVAMju2/39Sscc0TOWn2Tmy6y+lr6K+H503gf7Iv+MkGw+4tg6zGR m2WpShzr5OynMidvMNGStvTnW63qpyv14O00dqZJ6ZF9m+03xu/RaV/zZ9dXP13Zikyvjyfq z1dJLt1c+UZcUnj3T+7ILexr7e0qnOS5387cG2h8/u2V9Gxf+3Khz51bF+9UYinOSDTUYi4q TgQAvLy3amECAAA= Subject: Re: [dpdk-dev] [RESEND PATCH] vhost_user: Make sure that memory map is set before attempting address translation 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>, <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>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Wed, 13 Jan 2016 09:40:20 -0000 Hello! > Do you have examples for the malfunctioning clients? If so, could you > list them in the commit message? The only malfunctioning client was DPDK itself, with virtio for container RFC applied. The client-side problem has been fixed afterwards by http://dpdk.org/ml/archives/dev/2016-January/031169.html. See the RFC discussion thread. Kind regards, Pavel Fedin Senior Engineer Samsung Electronics Research center Russia