From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f68.google.com (mail-oi0-f68.google.com [209.85.218.68]) by dpdk.org (Postfix) with ESMTP id 76E5F1B4F6 for ; Thu, 28 Jun 2018 22:14:22 +0200 (CEST) Received: by mail-oi0-f68.google.com with SMTP id c6-v6so6405841oiy.0 for ; Thu, 28 Jun 2018 13:14:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uzZZdIeFnseGsolr50cC/88YAe1PB90gTBKoVuNimaI=; b=Hz1Sr11PiHj7lrXAlcmrh6+fm7ZqcAn9/mAMUoWMCkCS588tm0FcdZtglIIY4Yr/9O SQJbRpbMMd4z/8cmuKBa5/frnqxbl7JxBQI88Ed19kN02NRIcVXf9nl5Sb/9sUePvkPu yVrnV33vtKfqB5jrNPuF02cf7mo3kwSOOaYgk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uzZZdIeFnseGsolr50cC/88YAe1PB90gTBKoVuNimaI=; b=CQQFNjXyc+Qu6Mw4eJxF2O4LOtL5mFZMED68NQD8obObF21kB9om5e4KAWH97cRbCp D+K+lI3S/h5L1SU3oS+lqgZfONMA2Qjr7MXv5pCaPdW+zaVoRmKfcsJWXFB1R+AzvUuX VXfdQcQq1KlOo/TWPOgWRYYgSGHpIDrWSPvebvW7TZ2V+qY1KtZYJTtBoeokjYShMrRE OzipeeiKRMAOzV2HxrYCA7Nys23YJkXxqJAndtDjMlZfxMHicx+vEDKiUSIERp5Gq5S7 OYJuino2Iz9H4dZ/l/F9DjtP79QIJS3wWt/YoSWITpoOZ1g3e2529YirX3WJriG1HkBG I/SA== X-Gm-Message-State: APt69E21RqMhIMdGTrM0pjou33eu1tC6KgRoaIdPPyBaSrNRlJHtH8py df1rPA8tfg4LfkCrXsLU9xbTzIbn/kHNDh+JjRj4AQ== X-Google-Smtp-Source: AAOMgpdvbDefFQsqtvFuep5JBItZ0dJ0qEacS0hs8NLHjJte6gmF1eEqSgd625RnISAm1BT4B+DlNZbTfN7xzZj33cU= X-Received: by 2002:aca:3544:: with SMTP id c65-v6mr6285762oia.326.1530216861643; Thu, 28 Jun 2018 13:14:21 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:3d05:0:0:0:0:0 with HTTP; Thu, 28 Jun 2018 13:13:41 -0700 (PDT) In-Reply-To: <0f973aac-48f7-5da0-34bf-8ffbed614025@intel.com> References: <20180619213058.12273-1-ajit.khaparde@broadcom.com> <20180619213058.12273-29-ajit.khaparde@broadcom.com> <0f973aac-48f7-5da0-34bf-8ffbed614025@intel.com> From: Ajit Khaparde Date: Thu, 28 Jun 2018 13:13:41 -0700 Message-ID: To: Ferruh Yigit Cc: dev@dpdk.org, dpdk stable Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-stable] [PATCH 28/31] net/bnxt: fix set MTU X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2018 20:14:22 -0000 On Tue, Jun 26, 2018 at 8:30 AM, Ferruh Yigit wrote: > On 6/19/2018 10:30 PM, Ajit Khaparde wrote: > > There is no need to update hardware configuration if new MTU is > > not greater than the max data the mbuf can accommodate. > > If app sets a smaller MTU won't it expect that HW will drop received > packets > bigger than provided size? Will this logic work if HW is not updated? > =E2=80=8BActually, the commit message needs rephrased. The behavior you mentioned will not be impacted. =E2=80=8BThe hardware will honor the MTU configured.=E2=80=8B