DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] Vhost app removes dependency of REFCNT
Date: Sat, 25 Oct 2014 01:01:35 +0000	[thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F96251187D063@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <11605757.Du0pTjUQ40@xps13>

Hi Thomas

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Friday, October 24, 2014 5:48 PM
> To: Ouyang, Changchun
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 0/3] Vhost app removes dependency of
> REFCNT
> 
> 2014-10-24 16:10, Ouyang Changchun:
> > To remove the dependency of RTE_MBUF_REFCNT for vhost zero copy,
> the
> > mbuf need introduce EXTERNAL_MBUF(in ol_flags) to indicate it attaches
> > to an external buffer, say, from guest space. And don't free the
> > external buffer when freeing the mbuf itself in host, in addition, RX
> > function in PMD need make sure not overwrite this flag when filling
> > ol_flags from descriptors to mbuf.
> 
> So you are replacing refcnt by something else which requires special handling
> in drivers.

To some extent, You are right, but I'd like regard as: our current mbuf implement has no consideration of external buffer. 
While vhost zero copy need it work well when it is external buffer, so need this special handling.
 Very appreciate if you have a better solution, design idea and let me know.  

> I feel this is not the right design.
> Why do you want to remove refcnt dependency?
> 
Bruce has some explanation about the reason in another mail.
For vhost zero copy itself, it doesn't depend on most of code REFCNT, it just need mbuf can support external buffer.
Before the change, undefine the REFCNT, make mbuf has workaround for supporting external buffer.

Thanks and regards,
Changchun

      parent reply	other threads:[~2014-10-25  0:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  8:10 Ouyang Changchun
2014-10-24  8:10 ` [dpdk-dev] [PATCH 1/3] mbuf: Use EXTERNAL_MBUF to indicate external buffer Ouyang Changchun
2014-10-24  8:10 ` [dpdk-dev] [PATCH 2/3] pmd: RX function need keep EXTERNAL_MBUF flag Ouyang Changchun
2014-10-24 10:46   ` Ananyev, Konstantin
2014-10-24 12:34     ` Bruce Richardson
2014-10-24 15:43       ` Bruce Richardson
2014-10-24 15:58         ` Ananyev, Konstantin
2014-10-25  2:08           ` Ouyang, Changchun
2014-10-24  8:10 ` [dpdk-dev] [PATCH 3/3] vhost: Removes dependency on REFCNT for zero copy Ouyang Changchun
2014-10-24  9:47 ` [dpdk-dev] [PATCH 0/3] Vhost app removes dependency of REFCNT Thomas Monjalon
2014-10-24 10:47   ` Bruce Richardson
2014-10-25  1:01   ` Ouyang, Changchun [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=F52918179C57134FAEC9EA62FA2F96251187D063@shsmsx102.ccr.corp.intel.com \
    --to=changchun.ouyang@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).