From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Confused about rtnl routing mutex scalability
Date: Wed, 7 Sep 2016 23:28:54 -0400 [thread overview]
Message-ID: <c503bba7-8081-acd3-6722-fc557d800e60@gmail.com> (raw)
Greetings All,
I am curious as it after reading the network code for a while it seems that to me
at least the rtnl mutex lock is a bottleneck. Is there any reason that we are still
using a global mutex for all routing changes in the networking stack for the Linux
kernel or does it actually scale only, seems to me that it is causing nothing but
problems with deadlocks related to it or issues with locking timeouts on separate
netdev routing tables for two different networks. Is this just me or does this lock
actually cause serious issues or can do so.
Regards,
Nick
next reply other threads:[~2016-09-08 3:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 3:28 nick [this message]
2016-09-11 1:50 ` Confused about rtnl routing mutex scalability Valdis.Kletnieks at vt.edu
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=c503bba7-8081-acd3-6722-fc557d800e60@gmail.com \
--to=xerofoify@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).