From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Andriy Berestovskyy <Andriy.Berestovskyy@caviumnetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Bruce Richardson <bruce.richardson@intel.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"arybchenko@solarflare.com" <arybchenko@solarflare.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"jerin.jacob@cavium.com" <jerin.jacob@cavium.com>
Subject: Re: [PATCH v3] ether: use a default for max Rx frame size in configure()
Date: Wed, 23 May 2018 10:53:35 +0530 [thread overview]
Message-ID: <20180523052333.GA12257@jerin> (raw)
In-Reply-To: <DB7PR05MB4426109FDE704ACB66A28D45C36B0@DB7PR05MB4426.eurprd05.prod.outlook.com>
-----Original Message-----
> Date: Wed, 23 May 2018 05:21:43 +0000
> From: Shahaf Shuler <shahafs@mellanox.com>
> To: Thomas Monjalon <thomas@monjalon.net>, Andriy Berestovskyy
> <Andriy.Berestovskyy@caviumnetworks.com>
> CC: "dev@dpdk.org" <dev@dpdk.org>, Bruce Richardson
> <bruce.richardson@intel.com>, "ferruh.yigit@intel.com"
> <ferruh.yigit@intel.com>, "arybchenko@solarflare.com"
> <arybchenko@solarflare.com>, "hemant.agrawal@nxp.com"
> <hemant.agrawal@nxp.com>, "jerin.jacob@cavium.com"
> <jerin.jacob@cavium.com>
> Subject: RE: [dpdk-dev] [PATCH v3] ether: use a default for max Rx frame
> size in configure()
>
> Hi Andriy,
>
> I think this patch addressing just small issue in a bigger problem.
> The way I see it all application needs to specify is the max packet size it expects to receive, nothing else(!).
+1
> Currently we are forcing it to toggle multiple redundant fields.
next prev parent reply other threads:[~2018-05-23 5:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 17:06 [PATCH] ether: fix configure() to use a default for max_rx_pkt_len Andriy Berestovskyy
2017-03-24 11:52 ` [PATCH v2] ether: use a default for max Rx frame size in configure() Andriy Berestovskyy
2017-03-27 6:15 ` Yang, Qiming
2017-03-27 8:38 ` Andriy Berestovskyy
2017-04-07 8:24 ` Bruce Richardson
2017-04-06 20:48 ` Thomas Monjalon
2017-04-07 8:09 ` Andriy Berestovskyy
2017-04-07 8:34 ` Thomas Monjalon
2017-04-07 8:55 ` Andriy Berestovskyy
2017-04-07 11:02 ` [PATCH v3] " Andriy Berestovskyy
2017-04-07 12:15 ` Thomas Monjalon
2017-04-07 12:29 ` Bruce Richardson
2017-04-07 14:18 ` Andriy Berestovskyy
2017-04-07 14:47 ` Thomas Monjalon
2017-04-07 15:27 ` Andriy Berestovskyy
2017-04-20 22:25 ` Thomas Monjalon
2017-04-24 14:50 ` Andriy Berestovskyy
2017-07-31 22:33 ` Thomas Monjalon
2018-05-22 22:30 ` Thomas Monjalon
2018-05-23 5:21 ` Shahaf Shuler
2018-05-23 5:23 ` Jerin Jacob [this message]
2018-05-24 9:20 ` Andriy Berestovskyy
2019-01-23 18:36 ` Ferruh Yigit
2019-01-25 21:15 ` Andriy Berestovskyy
2017-04-10 14:30 ` [PATCH 1/3] examples/ip_fragmentation: limit max frame size Andriy Berestovskyy
2017-04-10 14:30 ` [PATCH 2/3] examples/ip_reassembly: " Andriy Berestovskyy
2017-04-10 14:30 ` [PATCH 3/3] examples/ipv4_multicast: " Andriy Berestovskyy
2017-04-21 0:21 ` [PATCH 1/3] examples/ip_fragmentation: " Thomas Monjalon
2023-06-08 16:51 ` [PATCH v3] ether: use a default for max Rx frame size in configure() Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180523052333.GA12257@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=Andriy.Berestovskyy@caviumnetworks.com \
--cc=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@cavium.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.