From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>,
david.marchand@6wind.com, adrien.mazarguil@6wind.com,
nelio.laranjeiro@6wind.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/2] net/mlx5 add rxq interrupt support
Date: Thu, 9 Feb 2017 14:48:18 +0000 [thread overview]
Message-ID: <4b821c2d-91ef-fe6b-7169-8af225f98e2a@intel.com> (raw)
In-Reply-To: <1486562252-15307-1-git-send-email-shahafs@mellanox.com>
On 2/8/2017 1:57 PM, Shahaf Shuler wrote:
> This patchset adds support for rxq interrupts on MLX5 PMD.
> The first patch introduces changes on eal_interrupt to support external interrupt handlers.
> The second patch implements the support on mlx5 PMD and demonstrate the use of the changes made in the first patch
>
> [PATCH 1/2] eal_interrupts: support external rxq interrupt handlers
> [PATCH 2/2] net/mlx5: support user space rxq interrupt event
Hi Shahaf,
I assume this patch is for 17.05 release, can you please confirm?
Thanks,
ferruh
next prev parent reply other threads:[~2017-02-09 14:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 13:57 Shahaf Shuler
2017-02-08 13:57 ` [dpdk-dev] [PATCH 1/2] eal_interrupts: support external rxq interrupt handlers Shahaf Shuler
2017-03-09 18:10 ` Thomas Monjalon
2017-03-12 8:30 ` Shahaf Shuler
2017-03-14 12:32 ` Ferruh Yigit
2017-02-08 13:57 ` [dpdk-dev] [PATCH 2/2] net/mlx5: support user space rxq interrupt event Shahaf Shuler
2017-02-09 14:48 ` Ferruh Yigit [this message]
2017-02-12 7:08 ` [dpdk-dev] [PATCH 0/2] net/mlx5 add rxq interrupt support Shahaf Shuler
2017-02-21 11:40 ` Shahaf Shuler
2017-02-28 7:29 ` Shahaf Shuler
2017-03-14 13:03 ` [dpdk-dev] [PATCH v2 " Shahaf Shuler
2017-03-14 13:03 ` [dpdk-dev] [PATCH v2 1/2] eal/linux: support external Rx interrupt Shahaf Shuler
2017-03-14 16:38 ` Yongseok Koh
2017-03-14 18:06 ` Ferruh Yigit
2017-03-14 13:03 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: support user space rxq interrupt event Shahaf Shuler
2017-03-14 16:39 ` Yongseok Koh
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=4b821c2d-91ef-fe6b-7169-8af225f98e2a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=shahafs@mellanox.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).