DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Igor Ryzhov <iryzhov@nfware.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] config: set RTE_KNI_PREEMPT_DEFAULT in meson
Date: Wed, 18 Sep 2019 11:32:59 +0100	[thread overview]
Message-ID: <20190918103258.GA1937@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAF+s_Fwhuy536QYrNLYX2NV1Adt6QrL0=7dzSKUqLXz5iwWtuQ@mail.gmail.com>

On Tue, Sep 17, 2019 at 10:11:04PM +0300, Igor Ryzhov wrote:
>    CCing Bruce, maintainer of the meson build system.
>    It's a simple patch to make meson behavior consistent with make
>    behavior.
>    CONFIG_RTE_KNI_PREEMPT_DEFAULT is set to "y" in config/common_base,
>    so we need to set RTE_KNI_PREEMPT_DEFAULT to 1 in meson.
>    Best regards,
>    Igor
> 
No objection from me.

Acked-by: Bruce Richardson <bruce.richardson@intel.com>

>    On Mon, Sep 16, 2019 at 1:08 PM Igor Ryzhov <[1]iryzhov@nfware.com>
>    wrote:
> 
>      Same behavior as in make build system.
>      Signed-off-by: Igor Ryzhov <[2]iryzhov@nfware.com>
>      ---
>       config/rte_config.h | 3 +++
>       1 file changed, 3 insertions(+)
>      diff --git a/config/rte_config.h b/config/rte_config.h
>      index 0bbbe274f..e6a35a170 100644
>      --- a/config/rte_config.h
>      +++ b/config/rte_config.h
>      @@ -98,6 +98,9 @@
>       #define RTE_SCHED_PORT_N_GRINDERS 8
>       #undef RTE_SCHED_VECTOR
>      +/* rte_kni defines */
>      +#define RTE_KNI_PREEMPT_DEFAULT 1
>      +
>       /****** driver defines ********/
>       /* QuickAssist device */
>      --
>      2.23.0
> 
> References
> 
>    1. mailto:iryzhov@nfware.com
>    2. mailto:iryzhov@nfware.com

  reply	other threads:[~2019-09-18 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16 10:08 Igor Ryzhov
2019-09-17 19:11 ` Igor Ryzhov
2019-09-18 10:32   ` Bruce Richardson [this message]
2019-10-23 23:14     ` 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=20190918103258.GA1937@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=iryzhov@nfware.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).