From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal: make max interrupt vectors configurable
Date: Tue, 26 Mar 2019 13:08:19 +0000 [thread overview]
Message-ID: <71f16f4bc027af328696a3eb6a24bc22cf90c022.camel@marvell.com> (raw)
Message-ID: <20190326130819.VFLnqC79eQf8rH2goYVadDbEYmdyt2F1c6JYDBvXDzE@z> (raw)
In-Reply-To: <20190326125327.5264-1-pbhagavatula@marvell.com>
On Tue, 2019-03-26 at 12:54 +0000, Pavan Nikhilesh Bhagavatula wrote:
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Make max interrupt vectors configurable so that platforms can
> choose interrupt vector limit.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
> config/common_base
Please update meson config too.
next prev parent reply other threads:[~2019-03-26 13:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 12:54 Pavan Nikhilesh Bhagavatula
2019-03-26 12:54 ` Pavan Nikhilesh Bhagavatula
2019-03-26 13:08 ` Jerin Jacob Kollanukkaran [this message]
2019-03-26 13:08 ` Jerin Jacob Kollanukkaran
2019-03-26 13:11 ` Pavan Nikhilesh Bhagavatula
2019-03-26 13:11 ` Pavan Nikhilesh Bhagavatula
2019-03-26 13:21 ` [dpdk-dev] [PATCH v2] " Pavan Nikhilesh Bhagavatula
2019-03-26 13:21 ` Pavan Nikhilesh Bhagavatula
2019-03-26 14:04 ` Thomas Monjalon
2019-03-26 14:04 ` Thomas Monjalon
2019-03-26 14:43 ` Bruce Richardson
2019-03-26 14:43 ` Bruce Richardson
2019-03-26 15:57 ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-03-26 15:57 ` Jerin Jacob Kollanukkaran
2019-03-31 14:55 ` [dpdk-dev] [PATCH v3] eal: increase max number of interrupt vectors Pavan Nikhilesh Bhagavatula
2019-03-31 14:55 ` Pavan Nikhilesh Bhagavatula
2019-04-02 12:32 ` Thomas Monjalon
2019-04-02 12:32 ` 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=71f16f4bc027af328696a3eb6a24bc22cf90c022.camel@marvell.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=pbhagavatula@marvell.com \
--cc=thomas@monjalon.net \
/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).