netdev - Re: [PATCH net-next v6 00/11] Modify action API for implementing lockless actions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20180708.124325.344679298289898945.davem@davemloft.net>
Date:   Sun, 08 Jul 2018 12:43:25 +0900 (KST)
From:   David Miller <davem@...emloft.net>
To:     vladbu@...lanox.com
Cc:     netdev@...r.kernel.org, jhs@...atatu.com, xiyou.wangcong@...il.com,
        jiri@...nulli.us, ast@...nel.org, daniel@...earbox.net,
        kliteyn@...lanox.com
Subject: Re: [PATCH net-next v6 00/11] Modify action API for implementing
 lockless actions

From: Vlad Buslov <vladbu@...lanox.com>
Date: Thu,  5 Jul 2018 17:24:22 +0300

> Currently, all netlink protocol handlers for updating rules, actions and
> qdiscs are protected with single global rtnl lock which removes any
> possibility for parallelism. This patch set is a first step to remove
> rtnl lock dependency from TC rules update path.
 ...

I'll apply this for now, I reviewed it a few more times and I see
where you are going with this.

I hope there are no new performance regressions in the control path
for cases people care about, and if there are I definitely expect
you to address them.

Thank you.