From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f182.google.com (mail-pf0-f182.google.com [209.85.192.182]) by dpdk.org (Postfix) with ESMTP id DD8FB2952 for ; Tue, 29 Mar 2016 03:37:56 +0200 (CEST) Received: by mail-pf0-f182.google.com with SMTP id x3so1579543pfb.1 for ; Mon, 28 Mar 2016 18:37:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=dzw/Oe8i7sIIA4IXKlq0gIhvE2kYw3EwaOTWKyBVBWE=; b=dA4bnUpnaZU29Zmk3PZk5XEd8Vf72B0hPUM9fvx/7WWN69so4BokzFZtzVYu4b268w 3Wt/QKV5ZuERoiJFrwv/+pzxW/AIU5r2KXFVu3w7WqhNYfC15yDXoTWjYKk8w/lL0Un6 VrMw3p2kpNDnr0ukEE/GBonjWIMyTxb6l9kZRbufWUj+WECe9hfJgtKMXPr8wBd6tLlZ rWssVD3lTphBwdiJEqJ/xIdGMRq+5TsQObYWgHOj9+DBiEEWkHQNSAzl/4C68CqQvpwy O4PhKhDo+ESZPhQf0CDXyyX5RGmWDPEUp7Dv980nyUwVM+5riGWJdnWXBkEmLgTA5XDE ayOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=dzw/Oe8i7sIIA4IXKlq0gIhvE2kYw3EwaOTWKyBVBWE=; b=A+L6MOWHkKTbPNkWcSQliwfJl8YBHSaAX/qWXjvneXNztv89n/B0G3CNExmjK8Fk97 zkxHkJapxNlRq5ZEoQNuqZTZBYzohGsULOStVahBM2u0zjsXF8ZhQRY2c/YlZrVnAjab 2qI+YQR6Xa1oEk5mD/JRc0OfjhjmWooI/1aqGppFHf+xFKgMRZGk41T+faZhZ6/oTscD ASlQm6Vm29Hl4v14N37OB+/4iEiuWMikMAqQMcexK97qbsI099Zw1chCwiyIFiCt26wk zm4IwxeIIWGOVbVpqn3SNy8cqhVWK5q/1yics2IzxzJDlDfoBhaoZdF8Kd0eN+P/GUt0 lqYQ== X-Gm-Message-State: AD7BkJKLv73UjWoeiWa+bVXBojwVw6eJkqRtcDen2IE9OkBAKqO0Df21jkuZrD72ZQv7kw== X-Received: by 10.98.17.78 with SMTP id z75mr48217982pfi.40.1459215476216; Mon, 28 Mar 2016 18:37:56 -0700 (PDT) Received: from ?IPv6:2602:304:b36d:9040:c5d7:dd83:1ce1:e152? ([2602:304:b36d:9040:c5d7:dd83:1ce1:e152]) by smtp.gmail.com with ESMTPSA id ll7sm38551972pab.6.2016.03.28.18.37.54 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 28 Mar 2016 18:37:55 -0700 (PDT) Content-Type: text/plain; charset=gb2312 Mime-Version: 1.0 (1.0) From: Clearasu X-Mailer: iPhone Mail (12B440) In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09090343FA66@shsmsx102.ccr.corp.intel.com> Date: Mon, 28 Mar 2016 18:37:53 -0700 Cc: "dev@dpdk.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <6A0DE07E22DDAD4C9103DF62FEBC09090343FA66@shsmsx102.ccr.corp.intel.com> To: "Lu, Wenzhuo" Subject: Re: [dpdk-dev] is ixgbe supporting multi-segment mbuf? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2016 01:37:57 -0000 Hi Wenzhuo, Thanks. For some reason, we have to stick to dpdk 2.0 for now. Is multi-segm= ent mbuf supported in this version (any known issue with multi-seg in this v= ersion?) or do we have to upgrade to latest dpdk version for multi-segment s= upport?=20 Clarylin > On Mar 28, 2016, at 6:10 PM, Lu, Wenzhuo wrote: >=20 >=20 > Hi Clarylin, >=20 >=20 >> -----Original Message----- >> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Clarylin L >> Sent: Tuesday, March 29, 2016 4:24 AM >> To: dev@dpdk.org >> Subject: [dpdk-dev] is ixgbe supporting multi-segment mbuf? >>=20 >> ixgbe_recv_scattered_pkts was set to be the rx function. Receiving packet= s > I see this function is already deprecated. Do you use an old version? Woul= d you like to try the newest code? >=20 >> smaller than mbuf size works perfectly. However, if an incoming packet is= >> greater than the maximum acceptable length of one =A1=B0mbuf=A1=B1 data s= ize, receiving >> does not work. In this case, isn't it supposed to use mbuf chaining to re= ceive? >>=20 >> The port has both jumbo_frame and enable_scatter being on. are these two >> flags good enough to make mbuf chaining going?