From: Thomas Monjalon <thomas@monjalon.net>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Cc: dev@dpdk.org, Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] eal: increase max number of interrupt vectors
Date: Tue, 02 Apr 2019 14:32:11 +0200 [thread overview]
Message-ID: <2596857.DnLQL2r5Jq@xps> (raw)
Message-ID: <20190402123211.4d5o6WeAlRVOesmiqrORlnFF8LXa6sSC3j42_5C2AFU@z> (raw)
In-Reply-To: <20190331145452.4144-1-pbhagavatula@marvell.com>
31/03/2019 16:55, Pavan Nikhilesh Bhagavatula:
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> MSI-X permits a device to allocate up to 2048 interrupts as per PCIe
> spec.
> Increase the max number of vectors to a reasonable value of 512.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Applied, thanks
next prev parent reply other threads:[~2019-04-02 12:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 12:54 [dpdk-dev] [PATCH] eal: make max interrupt vectors configurable Pavan Nikhilesh Bhagavatula
2019-03-26 12:54 ` Pavan Nikhilesh Bhagavatula
2019-03-26 13:08 ` Jerin Jacob Kollanukkaran
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 [this message]
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=2596857.DnLQL2r5Jq@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.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).