DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Chas Williams <3chas3@gmail.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [v3, PATCH 1/2] build: add option to override max ethports
Date: Tue, 26 Feb 2019 21:19:49 +0100	[thread overview]
Message-ID: <14936226.bhGOEySNNK@xps> (raw)
In-Reply-To: <20190207155318.12579-1-3chas3@gmail.com>

07/02/2019 16:53, Chas Williams:
> Allow users and packagers to override the default RTE_MAX_ETHPORTS.
> This adds a new meson option, max_ethports which defaults to the
> current value.
> 
> Signed-off-by: Chas Williams <3chas3@gmail.com>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> --- a/meson_options.txt
> +++ b/meson_options.txt
> +option('max_ethports', type: 'string', value: '32',
> +	description: 'maximum number of Ethernet devices in EAL')

Removing (while applying) "in EAL" because it is in ethdev lib.

      parent reply	other threads:[~2019-02-26 20:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31  2:18 [dpdk-dev] [PATCH] " Chas Williams
2019-01-31  9:32 ` Bruce Richardson
2019-01-31 23:26   ` Chas Williams
2019-02-04  9:46     ` Bruce Richardson
2019-02-06 17:10   ` Luca Boccassi
2019-01-31 23:53 ` [dpdk-dev] [PATCH 1/2 v2] " Chas Williams
2019-02-04  9:49   ` Bruce Richardson
2019-02-05 21:08     ` Chas Williams
2019-01-31 23:59 ` [dpdk-dev] [PATCH 2/2,v2] build: fix option ordering Chas Williams
2019-02-04  9:56   ` Bruce Richardson
2019-02-07 15:53 ` [dpdk-dev] [v3, PATCH 1/2] build: add option to override max ethports Chas Williams
2019-02-07 15:53   ` [dpdk-dev] [v3,PATCH 2/2] build: fix option ordering Chas Williams
2019-02-07 16:35     ` Bruce Richardson
2019-02-26 20:31       ` Thomas Monjalon
2019-02-26 20:19   ` 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=14936226.bhGOEySNNK@xps \
    --to=thomas@monjalon.net \
    --cc=3chas3@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.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).