DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: huawei.xie@intel.com, changchun.ouyang@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mbuf: clean old refcnt option
Date: Wed, 01 Apr 2015 21:58:04 +0200	[thread overview]
Message-ID: <2662680.fVrczecCFl@xps13> (raw)
In-Reply-To: <551AF4EF.5090104@6wind.com>

2015-03-31 21:26, Olivier MATZ:
> Hi Thomas,
> 
> On 03/31/2015 07:58 PM, Thomas Monjalon wrote:
> > CONFIG_RTE_MBUF_SCATTER_GATHER was renamed into CONFIG_RTE_MBUF_REFCNT
> > by commit 62814bc2e923 and removed by commit 4769bc5a27cc.
> > Some traces remain because of delayed patches.
> > 
> > It can also be removed from doxygen config.
> > It is now poisoned in rte_mbuf.h to warn any misuse.
> > 
> > Fixes: d0dff9ba445e ("doc: sample application user guide")
> > Fixes: fc1f2750a3ec ("doc: programmers guide")
> > Fixes: 4769bc5a27cc ("mbuf: remove build option to disable refcnt")
> > 
> > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
[...]
> > --- a/doc/guides/sample_app_ug/vhost.rst
> > +++ b/doc/guides/sample_app_ug/vhost.rst
> > @@ -338,28 +338,6 @@ Compiling the Sample Code
> >  
> >      .. code-block:: console
> >  
> > -        make
> > -
> > -    .. note::
> > -
> > -        Note For zero copy, need firstly disable CONFIG_RTE_MBUF_SCATTER_GATHER,
> > -        CONFIG_RTE_LIBRTE_IP_FRAG and CONFIG_RTE_LIBRTE_DISTRIBUTOR
> > -        in the config file and then re-configure and compile the core lib, and then build the application:
> > -
> > -    .. code-block:: console
> > -
> > -        vi ${RTE_SDK}/config/common_linuxapp
> > -
> > -    change it as follows:
> > -
> > -    ::
> > -
> > -        CONFIG_RTE_MBUF_SCATTER_GATHER=n
> > -        CONFIG_RTE_LIBRTE_IP_FRAG=n
> > -        CONFIG_RTE_LIBRTE_DISTRIBUTOR=n
> > -
> > -    .. code-block:: console
> > -
> >          cd ${RTE_SDK}
> >          make config ${RTE_TARGET}
> >          make install ${RTE_TARGET}

Note that make config is useless and T= is missing.

> I have one doubt about the vhost part, as the previous doc was telling
> to disable refcnt option and now the behavior is equivalent to having
> the option always enabled. Also you are removing parts of doc that
> talk about CONFIG_RTE_LIBRTE_DISTRIBUTOR and CONFIG_RTE_LIBRTE_IP_FRAG.
> 
> It would be safer to also have an acknowledgment from a vhost expert.

Huawei, Changchun, any opinion please?

  reply	other threads:[~2015-04-01 19:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 17:58 Thomas Monjalon
2015-03-31 19:26 ` Olivier MATZ
2015-04-01 19:58   ` Thomas Monjalon [this message]
2015-04-02 14:37     ` Butler, Siobhan A
2015-04-03  5:10     ` Ouyang, Changchun
2015-04-03 13:57       ` Thomas Monjalon

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=2662680.fVrczecCFl@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=changchun.ouyang@intel.com \
    --cc=dev@dpdk.org \
    --cc=huawei.xie@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).