From: Vinicius Tinti <viniciustinti@gmail.com>
To: "David S. Miller" <davem@davemloft.net>,
David Ahern <dsa@cumulusnetworks.com>,
Taehee Yoo <ap420073@gmail.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: Vinicius Tinti <viniciustinti@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Subject: Similar functions in net/core/dev.c
Date: Fri, 26 Feb 2021 14:09:54 +0000 [thread overview]
Message-ID: <20210226140954.GA752212@llvm-development.us-central1-a.c.llvm-285123.internal> (raw)
Hi,
All these functions in net/core/dev.c are very similar.
__netdev_walk_all_upper_dev
netdev_walk_all_upper_dev_rcu
netdev_walk_all_lower_dev
__netdev_walk_all_lower_dev
netdev_walk_all_lower_dev_rcu
Can they be merged in one function? Are they a hot path?
Regards,
Vinicius
reply other threads:[~2021-02-26 14:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210226140954.GA752212@llvm-development.us-central1-a.c.llvm-285123.internal \
--to=viniciustinti@gmail.com \
--cc=ap420073@gmail.com \
--cc=clang-built-linux@googlegroups.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.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).