From: Thomas Monjalon <thomas@monjalon.net>
To: "Patil, Harish" <Harish.Patil@cavium.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
"Jacob, Jerin" <Jerin.JacobKollanukkaran@cavium.com>,
"Thotton, Shijith" <Shijith.Thotton@cavium.com>,
"Shukla, Santosh" <Santosh.Shukla@cavium.com>,
Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
John Daley <johndale@cisco.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
Yongseok Koh <yskoh@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Tomasz Duszynski <tdu@semihalf.com>,
Jianbo Liu <jianbo.liu@arm.com>,
Alejandro Lucero <alejandro.lucero@netronome.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Shreyansh Jain <shreyansh.jain@nxp.com>,
"Mody, Rasesh" <Rasesh.Mody@cavium.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Shrikrishna Khare <skhare@vmware.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Allain Legacy <allain.legacy@windriver.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Gaetan Rivet <gaetan.rivet@6wind.com>,
Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] Survey for final decision about per-port offload API
Date: Mon, 02 Apr 2018 22:10:14 +0200 [thread overview]
Message-ID: <3635124.eX5m4pFW80@xps> (raw)
In-Reply-To: <D6E7B50D.1BC853%Harish.Patil@cavium.com>
02/04/2018 19:39, Patil, Harish:
> >It was also proposed to relax the API and allow "forgetting" port
> >offloads in queue offloads:
> > http://dpdk.org/ml/archives/dev/2018-March/092978.html
> >
> >It would mean the offloads applied to a queue result of OR operation:
> > rte_eth_conf.[rt]xmode.offloads | rte_eth_[rt]xconf.offloads
> >
> >1/ Do you agree with above API change?
>
> Yes. But pls confirm that this would still work properly if RX supports
> port-only based offloads and doesn’t support queue based offloads at all,
> as advertised in dev_infos_get().
>
> dev_info->rx_queue_offload_capa = 0 and
> dev_info->rx_offload_capa = (DEV_RX_OFFLOAD_IPV4_CKSUM | ...);
Yes, of course, no queue offload at all is possible.
next prev parent reply other threads:[~2018-04-02 20:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 13:47 Thomas Monjalon
2018-03-30 15:13 ` Andrew Rybchenko
2018-03-30 15:46 ` Thomas Monjalon
2018-04-01 1:51 ` Zhang, Qi Z
2018-04-02 15:44 ` Thomas Monjalon
2018-04-01 4:44 ` Shahaf Shuler
2018-04-02 15:53 ` Thomas Monjalon
2018-04-03 5:19 ` Shahaf Shuler
2018-04-02 1:27 ` Lu, Wenzhuo
2018-04-02 3:18 ` Xing, Beilei
2018-04-02 17:23 ` Wu, Jingjing
2018-04-02 17:39 ` Patil, Harish
2018-04-02 20:10 ` Thomas Monjalon [this message]
2018-04-02 20:45 ` Patil, Harish
2018-04-03 0:53 ` Zhang, Qi Z
2018-04-03 19:59 ` John Daley (johndale)
2018-04-04 0:25 ` Yongseok Koh
2018-04-11 14:42 ` Olivier Matz
2018-04-11 15:17 ` Alejandro Lucero
2018-04-12 5:41 ` Jerin Jacob
2018-04-12 7:03 ` Maxime Coquelin
2018-04-12 9:08 ` Shreyansh Jain
2018-04-24 10:39 ` Ferruh Yigit
2018-04-24 11:08 ` Ananyev, Konstantin
2018-04-24 12:27 ` Ferruh Yigit
2018-04-24 15:20 ` Ananyev, Konstantin
2018-04-24 16:18 ` Ferruh Yigit
2018-04-24 12:56 ` Shahaf Shuler
2018-04-24 22:00 ` Thomas Monjalon
2018-04-25 13:32 ` Ferruh Yigit
2018-04-25 15:21 ` Thomas Monjalon
2018-04-25 16:45 ` 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=3635124.eX5m4pFW80@xps \
--to=thomas@monjalon.net \
--cc=Harish.Patil@cavium.com \
--cc=Jerin.JacobKollanukkaran@cavium.com \
--cc=Rasesh.Mody@cavium.com \
--cc=Santosh.Shukla@cavium.com \
--cc=Shijith.Thotton@cavium.com \
--cc=adrien.mazarguil@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=alejandro.lucero@netronome.com \
--cc=allain.legacy@windriver.com \
--cc=arybchenko@solarflare.com \
--cc=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.com \
--cc=hemant.agrawal@nxp.com \
--cc=jianbo.liu@arm.com \
--cc=jingjing.wu@intel.com \
--cc=johndale@cisco.com \
--cc=konstantin.ananyev@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=olivier.matz@6wind.com \
--cc=qi.z.zhang@intel.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=shahafs@mellanox.com \
--cc=shreyansh.jain@nxp.com \
--cc=skhare@vmware.com \
--cc=tdu@semihalf.com \
--cc=wenzhuo.lu@intel.com \
--cc=yskoh@mellanox.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).