From: "Ling, WeiX" <weix.ling@intel.com>
To: "Ding, Xuan" <xuan.ding@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"Xia, Chenbo" <chenbo.xia@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] net/vhost: fix compliant offloading flag
Date: Tue, 28 Jun 2022 10:58:49 +0000 [thread overview]
Message-ID: <PH7PR11MB6006BCA6A01E228C1414BF3EEEB89@PH7PR11MB6006.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BN9PR11MB5513A2FC3FC9289C0971260DE7B89@BN9PR11MB5513.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Ding, Xuan <xuan.ding@intel.com>
> Sent: Tuesday, June 28, 2022 6:29 PM
> To: Maxime Coquelin <maxime.coquelin@redhat.com>; Xia, Chenbo
> <chenbo.xia@intel.com>
> Cc: dev@dpdk.org; Ling, WeiX <weix.ling@intel.com>
> Subject: RE: [PATCH] net/vhost: fix compliant offloading flag
>
>
>
> > -----Original Message-----
> > From: Maxime Coquelin <maxime.coquelin@redhat.com>
> > Sent: Tuesday, June 28, 2022 5:57 PM
> > To: Ding, Xuan <xuan.ding@intel.com>; Xia, Chenbo
> > <chenbo.xia@intel.com>
> > Cc: dev@dpdk.org; Ling, WeiX <weix.ling@intel.com>
> > Subject: Re: [PATCH] net/vhost: fix compliant offloading flag
> >
> >
> >
> > On 6/28/22 11:42, xuan.ding@intel.com wrote:
> > > From: Xuan Ding <xuan.ding@intel.com>
> > >
> > > This patch fixes the check to set compliant offloading flag.
> > > Compliant offloading flag should be set when the 'legacy-ol-flags'
> > > is true.
> > >
> > > Fixes: 3a6ee8dafb21("net/vhost: enable compliant offloading mode")
> > >
> > > Signed-off-by: Xuan Ding <xuan.ding@intel.com>
> > > ---
Tested-by: Wei Ling <weix.ling@intel.com>
prev parent reply other threads:[~2022-06-28 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 9:42 xuan.ding
2022-06-28 9:57 ` Maxime Coquelin
2022-06-28 10:28 ` Ding, Xuan
2022-06-28 10:58 ` Ling, WeiX [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=PH7PR11MB6006BCA6A01E228C1414BF3EEEB89@PH7PR11MB6006.namprd11.prod.outlook.com \
--to=weix.ling@intel.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=xuan.ding@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).