From: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Patil, Harish" <Harish.Patil@cavium.com>,
Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnx2x: convert to new Rx offloads API
Date: Sat, 7 Apr 2018 05:09:05 +0000 [thread overview]
Message-ID: <MWHPR0701MB3675FA5C17CC49264D7468DB9FB90@MWHPR0701MB3675.namprd07.prod.outlook.com> (raw)
In-Reply-To: <1eef7193-10ee-66ac-cd7c-fb767c8fafaa@intel.com>
> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> Sent: Thursday, April 05, 2018 6:40 AM
>
> On 4/1/2018 7:03 AM, Rasesh Mody wrote:
> > From: Harish Patil <harish.patil@cavium.com>
> >
> > Ethdev RX offloads API has changed since:
> > commit ce17eddefc20 ("ethdev: introduce Rx queue offloads API")
> >
> > This patch makes use of DEV_RX_OFFLOAD_JUMBO_FRAME offload flag to
> > advertise jumbo frame support.
> >
> > Signed-off-by: Harish Patil <harish.patil@cavium.com>
> > ---
> > drivers/net/bnx2x/bnx2x_ethdev.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/bnx2x/bnx2x_ethdev.c
> > b/drivers/net/bnx2x/bnx2x_ethdev.c
> > index 483d5a1..fada4bd 100644
> > --- a/drivers/net/bnx2x/bnx2x_ethdev.c
> > +++ b/drivers/net/bnx2x/bnx2x_ethdev.c
> > @@ -140,11 +140,13 @@ struct rte_bnx2x_xstats_name_off {
> > bnx2x_dev_configure(struct rte_eth_dev *dev) {
> > struct bnx2x_softc *sc = dev->data->dev_private;
> > + struct rte_eth_rxmode *rxmode = &dev->data->dev_conf.rxmode;
> > +
> > int mp_ncpus = sysconf(_SC_NPROCESSORS_CONF);
> >
> > PMD_INIT_FUNC_TRACE();
> >
> > - if (dev->data->dev_conf.rxmode.jumbo_frame)
> > + if (rxmode & DEV_RX_OFFLOAD_JUMBO_FRAME)
>
> I guess you would mean "rxmode->offloads".
>
> Isn't this caught by automated build?
You are right, will send a v2 with proper offload check.
I do not think this was caught by automated build.
>
> > sc->mtu = dev->data->dev_conf.rxmode.max_rx_pkt_len;
> >
> > if (dev->data->nb_tx_queues > dev->data->nb_rx_queues) { @@ -
> 454,6
> > +456,7 @@ struct rte_bnx2x_xstats_name_off {
> > dev_info->max_rx_pktlen = BNX2X_MAX_RX_PKT_LEN;
> > dev_info->max_mac_addrs = BNX2X_MAX_MAC_ADDRS;
> > dev_info->speed_capa = ETH_LINK_SPEED_10G |
> ETH_LINK_SPEED_20G;
> > + dev_info->rx_offload_capa = DEV_RX_OFFLOAD_JUMBO_FRAME;
> > }
> >
> > static int
> >
next prev parent reply other threads:[~2018-04-07 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 6:03 Rasesh Mody
2018-04-05 13:40 ` Ferruh Yigit
2018-04-07 5:09 ` Mody, Rasesh [this message]
2018-04-09 5:37 ` [dpdk-dev] [PATCH v2] " Rasesh Mody
2018-04-10 16:33 ` Ferruh Yigit
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=MWHPR0701MB3675FA5C17CC49264D7468DB9FB90@MWHPR0701MB3675.namprd07.prod.outlook.com \
--to=rasesh.mody@cavium.com \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=Harish.Patil@cavium.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).