From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Zoltan Kiss <zoltan.kiss@linaro.org>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples/vhost: use library routines instead of local copies
Date: Thu, 26 Mar 2015 03:32:46 +0000 [thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F962511A76261@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB97725821407936@irsmsx105.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ananyev,
> Konstantin
> Sent: Thursday, March 26, 2015 9:21 AM
> To: Zoltan Kiss; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] examples/vhost: use library routines
> instead of local copies
>
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zoltan Kiss
> > Sent: Wednesday, March 25, 2015 6:43 PM
> > To: dev@dpdk.org
> > Cc: Zoltan Kiss
> > Subject: [dpdk-dev] [PATCH] examples/vhost: use library routines
> > instead of local copies
> >
> > This macro and function were copies from the mbuf library, no reason
> > to keep them.
>
> NACK
> You can't use RTE_MBUF_INDIRECT macro here.
> If you'll look at vhost code carefully, you'll realise that we don't use standard
> rte_pktmbuf_attach() here.
> As we attach mbuf not to another mbuf but to external memory buffer,
> passed to us by virtio device.
> Look at attach_rxmbuf_zcp().
> Though I suppose, we can replace pktmbuf_detach_zcp() , with
> rte_pktmbuf_detach() - they are doing identical things.
> BTW, I wonder did you ever test your patch?
> My guess it would cause vhost with '--zero-copy' to crash or corrupt the
> packets straightway.
>
> Konstantin
>
> >
> > Signed-off-by: Zoltan Kiss <zoltan.kiss@linaro.org>
NACK this patch,
Same reason with Konstantin.
Changchun
next prev parent reply other threads:[~2015-03-26 3:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 18:43 Zoltan Kiss
2015-03-26 1:20 ` Ananyev, Konstantin
2015-03-26 3:32 ` Ouyang, Changchun [this message]
2015-03-26 16:46 ` Zoltan Kiss
2015-03-26 17:34 ` Ananyev, Konstantin
2015-03-26 18:01 ` Zoltan Kiss
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=F52918179C57134FAEC9EA62FA2F962511A76261@shsmsx102.ccr.corp.intel.com \
--to=changchun.ouyang@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=zoltan.kiss@linaro.org \
/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).