From: "Björn Töpel" <bjorn.topel@intel.com>
To: Maxim Mikityanskiy <maximmi@mellanox.com>,
Magnus Karlsson <magnus.karlsson@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: "bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"David S. Miller" <davem@davemloft.net>,
Saeed Mahameed <saeedm@mellanox.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>
Subject: Re: [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
WARNING: multiple messages have this Message-ID (diff)
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: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 16:20 [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] " Maxim Mikityanskiy
2019-12-17 16:20 ` [PATCH bpf v2 1/4] xsk: Add rcu_read_lock around the XSK wakeup Maxim Mikityanskiy
2019-12-17 16:20 ` [Intel-wired-lan] " Maxim Mikityanskiy
2019-12-17 16:20 ` [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] " Maxim Mikityanskiy
2019-12-17 16:20 ` [PATCH bpf v2 3/4] net/i40e: " Maxim Mikityanskiy
2019-12-17 16:20 ` [Intel-wired-lan] " Maxim Mikityanskiy
2019-12-17 16:20 ` [PATCH bpf v2 4/4] net/ixgbe: " Maxim Mikityanskiy
2019-12-17 16:20 ` [Intel-wired-lan] " Maxim Mikityanskiy
2019-12-17 17:33 ` Björn Töpel [this message]
2019-12-17 17:33 ` [Intel-wired-lan] [PATCH bpf v2 0/4] Fix concurrency issues between XSK wakeup and control path using RCU =?unknown-8bit?q?Bj=C3=B6rn_T=C3=B6pel?=
2019-12-19 15:59 ` Daniel Borkmann
2019-12-19 15:59 ` [Intel-wired-lan] " 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=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jakub.kicinski@netronome.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=maximmi@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.