From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>, dev@dpdk.org
Cc: Georgiy Levashov <Georgiy.Levashov@oktetlabs.ru>
Subject: Re: [dpdk-dev] [PATCH 1/2] net/sfc: add Rx interrupts support for efx datapath
Date: Wed, 12 Jun 2019 08:56:06 +0100 [thread overview]
Message-ID: <8c19d7d7-1682-12d2-6cce-9d9e3ba3f047@intel.com> (raw)
In-Reply-To: <1559842405-7987-1-git-send-email-arybchenko@solarflare.com>
On 6/6/2019 6:33 PM, Andrew Rybchenko wrote:
> From: Georgiy Levashov <Georgiy.Levashov@oktetlabs.ru>
>
> When Rx interrupts are disabled, we simply disable rearm when
> the interrupt fires the next time. So, the next packet will
> trigger interrupt (if it is not happened yet after previous Rx
> burst processing).
>
> Signed-off-by: Georgiy Levashov <Georgiy.Levashov@oktetlabs.ru>
> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-06-12 7:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 17:33 Andrew Rybchenko
2019-06-06 17:33 ` [dpdk-dev] [PATCH 2/2] net/sfc: add Rx interrupts support for ef10 datapath Andrew Rybchenko
2019-06-12 7:56 ` Ferruh Yigit [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=8c19d7d7-1682-12d2-6cce-9d9e3ba3f047@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Georgiy.Levashov@oktetlabs.ru \
--cc=arybchenko@solarflare.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).