From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Li, Xiaoyun" <xiaoyun.li@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/avf: fix missing offload capabilities
Date: Thu, 2 Aug 2018 02:21:58 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E7061153262AD9@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09093B80C4C2@shsmsx102.ccr.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Lu, Wenzhuo
> Sent: Thursday, August 2, 2018 9:56 AM
> To: Li, Xiaoyun <xiaoyun.li@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] net/avf: fix missing offload capabilities
>
> Hi Xiaoyun,
>
>
> > -----Original Message-----
> > From: Li, Xiaoyun
> > Sent: Wednesday, August 1, 2018 9:35 AM
> > To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wu, Jingjing
> > <jingjing.wu@intel.com>
> > Cc: dev@dpdk.org; stable@dpdk.org
> > Subject: RE: [PATCH] net/avf: fix missing offload capabilities
> >
> > Hi
> >
> > > -----Original Message-----
> > > From: Lu, Wenzhuo
> > > Sent: Wednesday, August 1, 2018 09:19
> > > To: Li, Xiaoyun <xiaoyun.li@intel.com>; Wu, Jingjing
> > > <jingjing.wu@intel.com>
> > > Cc: dev@dpdk.org; stable@dpdk.org
> > > Subject: RE: [PATCH] net/avf: fix missing offload capabilities
> > >
> > > Hi Xiaoyun,
> > >
> > >
> > > > -----Original Message-----
> > > > From: Li, Xiaoyun
> > > > Sent: Wednesday, July 25, 2018 3:15 PM
> > > > To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wu, Jingjing
> > > > <jingjing.wu@intel.com>
> > > > Cc: dev@dpdk.org; Li, Xiaoyun <xiaoyun.li@intel.com>;
> > > > stable@dpdk.org
> > > > Subject: [PATCH] net/avf: fix missing offload capabilities
> > > >
> > > > There are several tx/rx offload capabilities missing in AVF.
> > > > Add them in this patch since AVF supports them.
> > > >
> > > > Fixes: 69dd4c3d0898 ("net/avf: enable queue and device")
> > > > Cc: stable@dpdk.org
> > > >
> > > > Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com>
> > > > ---
> > > > drivers/net/avf/avf_ethdev.c | 18 ++++++++++++++++--
> > > > 1 file changed, 16 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/drivers/net/avf/avf_ethdev.c
> > > > b/drivers/net/avf/avf_ethdev.c index 0e21f8c..3a2baaf 100644
> > > > --- a/drivers/net/avf/avf_ethdev.c
> > > > +++ b/drivers/net/avf/avf_ethdev.c
> > > > @@ -518,16 +518,30 @@ avf_dev_info_get(struct rte_eth_dev *dev,
> > > > struct rte_eth_dev_info *dev_info)
> > > > dev_info->max_mac_addrs = AVF_NUM_MACADDR_MAX;
> > > > dev_info->rx_offload_capa =
> > > > DEV_RX_OFFLOAD_VLAN_STRIP |
> > > > + DEV_RX_OFFLOAD_QINQ_STRIP |
> > > > DEV_RX_OFFLOAD_IPV4_CKSUM |
> > > > DEV_RX_OFFLOAD_UDP_CKSUM |
> > > > - DEV_RX_OFFLOAD_TCP_CKSUM;
> > > > + DEV_RX_OFFLOAD_TCP_CKSUM |
> > > > + DEV_RX_OFFLOAD_OUTER_IPV4_CKSUM |
> > > > + DEV_RX_OFFLOAD_CRC_STRIP |
> > > > + DEV_RX_OFFLOAD_KEEP_CRC |
> > > Don't find this flag. Does this path depend on another?
> > > Do we need to announce this capa?
> >
> > You mean KEEP_CRC? I copy the flags from i40evf.
> > In release note:
> > In v18.11 ``DEV_RX_OFFLOAD_CRC_STRIP`` offload flag will be removed,
> > default
> > behavior without any flag will be changed to CRC strip.
> > To keep CRC ``DEV_RX_OFFLOAD_KEEP_CRC`` flag is required.
> > ``KEEP_CRC``: Keep CRC in packet
> > No flag: Strip CRC from packet
> O, got the history.
> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
Applied to dpdk-next-net-intel.
Thanks!
Qi
prev parent reply other threads:[~2018-08-02 2:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 7:14 Xiaoyun Li
2018-08-01 1:18 ` Lu, Wenzhuo
2018-08-01 1:34 ` Li, Xiaoyun
2018-08-02 1:56 ` Lu, Wenzhuo
2018-08-02 2:21 ` Zhang, Qi Z [this message]
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=039ED4275CED7440929022BC67E7061153262AD9@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@intel.com \
--cc=xiaoyun.li@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).