From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Alexander Duyck <alexander.h.duyck@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [net-next PATCH] ixgbe: Drop unnecessary call to rcu_barrier
Date: Mon, 30 Mar 2015 11:35:58 -0700 [thread overview]
Message-ID: <1427740558.2497.91.camel@jtkirshe-mobl> (raw)
In-Reply-To: <20150330164138.1335.47547.stgit@ahduyck-vm-fedora22>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On Mon, 2015-03-30 at 09:41 -0700, Alexander Duyck wrote:
> The ixgbe driver hasn't used call_rcu to free the rings for some time
> now.
> Since that is the case the call to rcu_barrier can be dropped since
> calls
> to kfree_rcu don't require it.
>
> Signed-off-by: Alexander Duyck <alexander.h.duyck@redhat.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 2 --
> 1 file changed, 2 deletions(-)
Thanks Alex, I will add you patch to my queue.
--
git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue.git
dev-queue
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-30 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 16:41 [net-next PATCH] ixgbe: Drop unnecessary call to rcu_barrier Alexander Duyck
2015-03-30 18:35 ` Jeff Kirsher [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=1427740558.2497.91.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.h.duyck@redhat.com \
--cc=netdev@vger.kernel.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).