From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 6256E2965 for ; Sat, 30 Mar 2019 01:00:25 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id F267D21DB2; Fri, 29 Mar 2019 20:00:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 29 Mar 2019 20:00:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=qer4U4nVOMElnXo5+EBo9rmocuTaxlzM/17ZlSnvBjs=; b=rJS2f0jod7Bm bg0CtyfAHYt9Jx3xeQ4jTrdYbYYNSa1/zyE4b+u4yr3zemk3TKtjM/jLg/p4soRp /qvt377b+YMEMpUs5DVen2BYDylJS6nPKo1y0ELxyfYm8lGre3a5aDsehasMeOxN XhI8CekIu3y4uHE3hxs0GcKwE+yl0Pg= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=qer4U4nVOMElnXo5+EBo9rmocuTaxlzM/17ZlSnvB js=; b=0tTlt20ZTsRPuo1iMEjSJttGmVi0ZK1H30JbBVoMfMK05yAu7/jEH6kRM QeCgmhLdfDScqHeqDv3+9DhrMp+jYrl3mfrX0CxpAzvwVHwpm4IGSA3ASHxWhD5a VdlDNxKnG2/zLIzmEQxh0WnU1CcnyjaJWSE/KwrkX0wL3NNw8c7Jebp0LjUzULTF k1xmmPJ+2gr9QQO1Mf9rvDoIvUYK9C5ppoLpR15OGt9P4yM3a6Ldn8YfOyYGNnDS 4YbXdL6FBmIcK4W04iww5T+ho4/NsYS1PmZs+FffXCa+3S/BoCws1BtcjDxPuPYD 18A0NJ7Dl4eKng0qC9fvPQPesc3sQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkeekgdduiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B307B1030F; Fri, 29 Mar 2019 20:00:23 -0400 (EDT) From: Thomas Monjalon To: lironh@marvell.com Cc: dev@dpdk.org, Ferruh Yigit , walan@marvell.com Date: Sat, 30 Mar 2019 01:00:22 +0100 Message-ID: <1583987.qdoNeV79LG@xps> In-Reply-To: <8fbf0397-42b1-ba11-d7eb-34bf0b404355@intel.com> References: <1553546882-22702-1-git-send-email-lironh@marvell.com> <1553625610-18172-1-git-send-email-lironh@marvell.com> <8fbf0397-42b1-ba11-d7eb-34bf0b404355@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v6] net/kni: calc mbuf&mtu according to given mb_pool 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: Sat, 30 Mar 2019 00:00:26 -0000 26/03/2019 18:59, Ferruh Yigit: > On 3/26/2019 6:40 PM, lironh@marvell.com wrote: > > From: Liron Himi > > > > - mbuf_size and mtu are now being calculated according > > to the given mb-pool. > > > > - max_mtu is now being set according to the given mtu > > > > the above two changes provide the ability to work with jumbo frames > > > > Signed-off-by: Liron Himi > > Suggested title: > kni: calculate MTU from mbuf buffer size > > Acked-by: Ferruh Yigit Applied, thanks From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 28449A05D3 for ; Sat, 30 Mar 2019 01:00:29 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 72B5A2BD3; Sat, 30 Mar 2019 01:00:27 +0100 (CET) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 6256E2965 for ; Sat, 30 Mar 2019 01:00:25 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id F267D21DB2; Fri, 29 Mar 2019 20:00:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 29 Mar 2019 20:00:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=qer4U4nVOMElnXo5+EBo9rmocuTaxlzM/17ZlSnvBjs=; b=rJS2f0jod7Bm bg0CtyfAHYt9Jx3xeQ4jTrdYbYYNSa1/zyE4b+u4yr3zemk3TKtjM/jLg/p4soRp /qvt377b+YMEMpUs5DVen2BYDylJS6nPKo1y0ELxyfYm8lGre3a5aDsehasMeOxN XhI8CekIu3y4uHE3hxs0GcKwE+yl0Pg= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=qer4U4nVOMElnXo5+EBo9rmocuTaxlzM/17ZlSnvB js=; b=0tTlt20ZTsRPuo1iMEjSJttGmVi0ZK1H30JbBVoMfMK05yAu7/jEH6kRM QeCgmhLdfDScqHeqDv3+9DhrMp+jYrl3mfrX0CxpAzvwVHwpm4IGSA3ASHxWhD5a VdlDNxKnG2/zLIzmEQxh0WnU1CcnyjaJWSE/KwrkX0wL3NNw8c7Jebp0LjUzULTF k1xmmPJ+2gr9QQO1Mf9rvDoIvUYK9C5ppoLpR15OGt9P4yM3a6Ldn8YfOyYGNnDS 4YbXdL6FBmIcK4W04iww5T+ho4/NsYS1PmZs+FffXCa+3S/BoCws1BtcjDxPuPYD 18A0NJ7Dl4eKng0qC9fvPQPesc3sQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkeekgdduiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B307B1030F; Fri, 29 Mar 2019 20:00:23 -0400 (EDT) From: Thomas Monjalon To: lironh@marvell.com Cc: dev@dpdk.org, Ferruh Yigit , walan@marvell.com Date: Sat, 30 Mar 2019 01:00:22 +0100 Message-ID: <1583987.qdoNeV79LG@xps> In-Reply-To: <8fbf0397-42b1-ba11-d7eb-34bf0b404355@intel.com> References: <1553546882-22702-1-git-send-email-lironh@marvell.com> <1553625610-18172-1-git-send-email-lironh@marvell.com> <8fbf0397-42b1-ba11-d7eb-34bf0b404355@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v6] net/kni: calc mbuf&mtu according to given mb_pool 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190330000022.bDnGnvEGid1oIixGIltLE41v2UduFrTJg5Km6azayBo@z> 26/03/2019 18:59, Ferruh Yigit: > On 3/26/2019 6:40 PM, lironh@marvell.com wrote: > > From: Liron Himi > > > > - mbuf_size and mtu are now being calculated according > > to the given mb-pool. > > > > - max_mtu is now being set according to the given mtu > > > > the above two changes provide the ability to work with jumbo frames > > > > Signed-off-by: Liron Himi > > Suggested title: > kni: calculate MTU from mbuf buffer size > > Acked-by: Ferruh Yigit Applied, thanks