From: Tanner Love <tannerlove.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, Tanner Love <tannerlove@google.com>
Subject: [PATCH net-next,v2,0/2] net: update netdev_rx_csum_fault() print dump only once
Date: Wed, 26 May 2021 19:13:34 -0400 [thread overview]
Message-ID: <20210526231336.2772011-1-tannerlove.kernel@gmail.com> (raw)
From: Tanner Love <tannerlove@google.com>
First patch implements DO_ONCE_LITE to abstract uses of the ".data.once"
trick. It is defined in its own, new header file -- rather than
alongside the existing DO_ONCE in include/linux/once.h -- because
include/linux/once.h includes include/linux/jump_label.h, and this
causes the build to break for some architectures if
include/linux/once.h is included in include/linux/printk.h or
include/asm-generic/bug.h.
Second patch uses DO_ONCE_LITE in netdev_rx_csum_fault to print dump
only once.
This is a v2 of https://patchwork.kernel.org/project/netdevbpf/patch/20210422194738.2175542-2-tannerlove.kernel@gmail.com/
Tanner Love (2):
once: implement DO_ONCE_LITE for non-fast-path "do once" functionality
net: update netdev_rx_csum_fault() print dump only once
fs/xfs/xfs_message.h | 13 +++----------
include/asm-generic/bug.h | 37 +++++++------------------------------
include/linux/once_lite.h | 24 ++++++++++++++++++++++++
include/linux/printk.h | 23 +++--------------------
kernel/trace/trace.h | 13 +++----------
net/core/dev.c | 14 +++++++++-----
6 files changed, 49 insertions(+), 75 deletions(-)
create mode 100644 include/linux/once_lite.h
--
2.32.0.rc0.204.g9fa02ecfa5-goog
next reply other threads:[~2021-05-26 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 23:13 Tanner Love [this message]
2021-05-26 23:13 ` [PATCH net-next,v2,1/2] once: implement DO_ONCE_LITE for non-fast-path "do once" functionality Tanner Love
2021-05-27 23:27 ` Jakub Kicinski
2021-05-26 23:13 ` [PATCH net-next,v2,2/2] net: update netdev_rx_csum_fault() print dump only once Tanner Love
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=20210526231336.2772011-1-tannerlove.kernel@gmail.com \
--to=tannerlove.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tannerlove@google.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.