From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id DB00F2A6C for ; Wed, 5 Apr 2017 06:52:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1491367954; x=1522903954; h=from:subject:to:references:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=kYZc6P72irwchxJJOkuxvzDu55c+llfz/a0wA1OPNZI=; b=OqPj5v29iHeGmfJKhytHv6l7rOAXNvVnPM3SlfJzXl7KvthQ6m01mGEf cp0pY2jrrHF7nzqYoiui87c17Zf1UQ==; Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Apr 2017 21:52:32 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,277,1486454400"; d="scan'208";a="73778867" Received: from shwdeisgchi083.ccr.corp.intel.com (HELO [10.239.67.182]) ([10.239.67.182]) by orsmga004.jf.intel.com with ESMTP; 04 Apr 2017 21:52:31 -0700 From: "Tan, Jianfeng" To: Maxime Coquelin , aconole@redhat.com, sodey@sonusnet.com, yuanhan.liu@linux.intel.com, thomas.monjalon@6wind.com, dev@dpdk.org References: <20170213142820.8964-1-maxime.coquelin@redhat.com> <20170312163406.17714-1-maxime.coquelin@redhat.com> <20170312163406.17714-8-maxime.coquelin@redhat.com> Message-ID: <0e5df10f-c61f-b1cd-a604-148379485ef2@intel.com> Date: Wed, 5 Apr 2017 12:52:30 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: <20170312163406.17714-8-maxime.coquelin@redhat.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Subject: Re: [dpdk-dev] [PATCH v3 7/9] net/virtio: Add MTU feature support X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2017 04:52:34 -0000 Hi Maxime, Have some confusion about this feature. Please help confirm. (1) With this feature, we only support to advertise MTU value which is defined by QEMU to frontend and backend driver separately. (2) But it does not allow frontend driver to set a different MTU to QEMU and then to vhost backend. Correct? If it's correct, why not MTU works like (2)? Thanks, Jianfeng