From: =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?= <bjorn.topel@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH bpf v2 0/4] Fix concurrency issues between XSK wakeup and control path using RCU
Date: Tue, 17 Dec 2019 18:33:14 +0100 [thread overview]
Message-ID: <cfe64691-7a0f-5b8a-d511-ebe742cec3c0@intel.com> (raw)
In-Reply-To: <20191217162023.16011-1-maximmi@mellanox.com>
On 2019-12-17 17:20, Maxim Mikityanskiy wrote:
> This series addresses the issue described in the commit message of the
> first patch: lack of synchronization between XSK wakeup and destroying
> the resources used by XSK wakeup. The idea is similar to
> napi_synchronize. The series contains fixes for the drivers that
> implement XSK. I haven't tested the changes to Intel's drivers, so,
> Intel guys, please review them.
>
Max, thanks a lot for compiling the series on your vacation!
Cheers,
Bj?rn
next prev parent reply other threads:[~2019-12-17 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 16:20 [Intel-wired-lan] [PATCH bpf v2 0/4] Fix concurrency issues between XSK wakeup and control path using RCU Maxim Mikityanskiy
2019-12-17 16:20 ` [Intel-wired-lan] [PATCH bpf v2 1/4] xsk: Add rcu_read_lock around the XSK wakeup Maxim Mikityanskiy
2019-12-17 16:20 ` [Intel-wired-lan] [PATCH bpf v2 2/4] net/mlx5e: Fix concurrency issues between config flow and XSK Maxim Mikityanskiy
2019-12-17 16:20 ` [Intel-wired-lan] [PATCH bpf v2 3/4] net/i40e: " Maxim Mikityanskiy
2019-12-17 16:20 ` [Intel-wired-lan] [PATCH bpf v2 4/4] net/ixgbe: " Maxim Mikityanskiy
2019-12-17 17:33 ` =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?= [this message]
2019-12-19 15:59 ` [Intel-wired-lan] [PATCH bpf v2 0/4] Fix concurrency issues between XSK wakeup and control path using RCU Daniel Borkmann
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=cfe64691-7a0f-5b8a-d511-ebe742cec3c0@intel.com \
--to=bjorn.topel@intel.com \
--cc=intel-wired-lan@osuosl.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