From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ajit.khaparde@broadcom.com>
Received: from mail-oi0-f65.google.com (mail-oi0-f65.google.com
 [209.85.218.65]) by dpdk.org (Postfix) with ESMTP id 6FE241B4F2
 for <dev@dpdk.org>; Thu, 28 Jun 2018 22:14:22 +0200 (CEST)
Received: by mail-oi0-f65.google.com with SMTP id s198-v6so2516403oih.11
 for <dev@dpdk.org>; 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=ABkD8N3/i+MWowh0sFr73aC+SA1Nft7bMtwKjxmTD6Rbtuve0CL22Ni/EDhY9B44D+
 28ebj5w7Qwqz2J0SvQznLpqCLWELyGSZ2sK4Aq+iEQkrgpIGRhBneYUHG6FusG+OkhY9
 Mk7u/TcaL4HrhYIWoiFsGYk8KUIaZco0Dgzp3qlPTH9HvoPiVapVE6Eiv/bycDymuRdx
 kqsbJcICxjv20r54TcMskQTLQK+/9xURc/RrcqEtUFPEG25T2YhiqTb0qUD4kEyC1hMl
 OEJduP2tt8Pd79KLkveYmwUBOJZ37s1xmhn6AG/tI/GuuyPmJTHWe1+lafInwK2Qkxbs
 b8Yw==
X-Gm-Message-State: APt69E3vdjsGq2jvyAqv+hoNQkOBEQ/g0UhLh9+BtgqvEz98DbShyo4n
 U+tRHBrXwkRAN/aPS2sAA4Xd9ju6zqktahLb41XWZg==
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 <ajit.khaparde@broadcom.com>
Date: Thu, 28 Jun 2018 13:13:41 -0700
Message-ID: <CACZ4nhspCVFrm-vnmC_=YkWPZZwd=Pk-mCxqne4m1QxpoB4hiw@mail.gmail.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, dpdk stable <stable@dpdk.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [dpdk-dev] [PATCH 28/31] net/bnxt: fix set MTU
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2018 20:14:22 -0000

On Tue, Jun 26, 2018 at 8:30 AM, Ferruh Yigit <ferruh.yigit@intel.com>
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