From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/2] Removal of RTE_MBUF_REFCNT
Date: Mon, 23 Feb 2015 19:36:46 +0100 [thread overview]
Message-ID: <10033845.zAL0UFbZ4z@xps13> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB977258213EF713@irsmsx105.ger.corp.intel.com>
> > This patch tries to remove the RTE_MBUF_REFCNT config options and dependencies
> > by introducing a new mbuf flag IND_ATTACHED_MBUF that would indicate when the mbuf
> > is an indirect attached mbuf, to differentiate between indirect mbufs and mbufs
> > with external memory buffers (ie. vhost zero copy).
> >
> > Previous discussion:
> > http://dpdk.org/ml/archives/dev/2014-October/007127.html
> >
> > Currently for mbufs with refcnt, we cannot free mbufs with external memory
> > buffers (ie. vhost zero copy), as they are recognized as indirect
> > attached mbufs and therefore we free the direct mbuf it points to,
> > resulting in an error in the case of external memory buffers.
> >
> > We solve the issue by introducing the IND_ATTACHED_MBUF flag, which indicates
> > that the mbuf is an indirect attached mbuf pointing to another mbuf.
> > When we free an mbuf, we only free the direct mbuf if the flag is set.
> > Freeing an mbuf with external buffer is the same as freeing a non attached mbuf.
> > The flag is set during attach and clear on detach.
> >
> > So in the case of vhost zero copy where we have mbufs with external
> > buffers, by default we just free the mbuf and it is up to the user to deal with
> > the external buffer.
> >
> > v2:
> > - Add missing parenthesis to RTE_MBUF_INDIRECT macro
> >
> > Sergio Gonzalez Monroy (2):
> > mbuf: Introduce IND_ATTACHED_MBUF flag
> > Remove RTE_MBUF_REFCNT references
>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Applied, thanks
prev parent reply other threads:[~2015-02-23 18:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 16:08 [dpdk-dev] [PATCH " Sergio Gonzalez Monroy
2015-02-16 16:08 ` [dpdk-dev] [PATCH 1/2] mbuf: Introduce IND_ATTACHED_MBUF flag Sergio Gonzalez Monroy
2015-02-16 16:08 ` [dpdk-dev] [PATCH 2/2] Remove RTE_MBUF_REFCNT references Sergio Gonzalez Monroy
2015-02-18 9:16 ` Olivier MATZ
2015-02-18 9:35 ` Bruce Richardson
2015-02-18 9:48 ` Ananyev, Konstantin
2015-02-18 10:00 ` Bruce Richardson
2015-02-18 10:14 ` Olivier MATZ
2015-02-18 10:22 ` Ananyev, Konstantin
2015-02-18 10:22 ` Bruce Richardson
2015-02-18 10:33 ` Olivier MATZ
2015-02-18 10:37 ` Bruce Richardson
2015-02-18 10:47 ` Olivier MATZ
2015-02-18 10:47 ` Ananyev, Konstantin
2015-02-18 11:01 ` Olivier MATZ
2015-02-18 9:52 ` Olivier MATZ
2015-02-16 20:47 ` [dpdk-dev] [PATCH 0/2] Removal of RTE_MBUF_REFCNT Stephen Hemminger
2015-02-17 8:43 ` Gonzalez Monroy, Sergio
2015-02-18 11:03 ` [dpdk-dev] [PATCH v2 " Sergio Gonzalez Monroy
2015-02-18 11:03 ` [dpdk-dev] [PATCH v2 1/2] mbuf: Introduce IND_ATTACHED_MBUF flag Sergio Gonzalez Monroy
2015-02-18 11:03 ` [dpdk-dev] [PATCH v2 2/2] Remove RTE_MBUF_REFCNT references Sergio Gonzalez Monroy
2015-02-18 12:05 ` [dpdk-dev] [PATCH v2 0/2] Removal of RTE_MBUF_REFCNT Ananyev, Konstantin
2015-02-23 18:36 ` Thomas Monjalon [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=10033845.zAL0UFbZ4z@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=sergio.gonzalez.monroy@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).