Searched hist:f4fee216df7d28b87d1c9cc60bcebfecb51c1a05 (Results 1 – 2 of 2) sorted by relevance
| /linux/security/apparmor/include/ |
| H A D | cred.h | diff f4fee216df7d28b87d1c9cc60bcebfecb51c1a05 Thu Jun 20 19:15:27 CEST 2024 Mateusz Guzik <mjguzik@gmail.com> apparmor: try to avoid refing the label in apparmor_file_open
If the label is not stale (which is the common case), the fact that the
passed file object holds a reference can be leverged to avoid the
ref/unref cycle. Doing so reduces performance impact of apparmor on
parallel open() invocations.
When benchmarking on a 24-core vm using will-it-scale's open1_process
("Separate file open"), the results are (ops/s):
before: 6092196
after: 8309726 (+36%)
Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
Signed-off-by: John Johansen <john.johansen@canonical.com>
|
| /linux/security/apparmor/ |
| H A D | lsm.c | diff f4fee216df7d28b87d1c9cc60bcebfecb51c1a05 Thu Jun 20 19:15:27 CEST 2024 Mateusz Guzik <mjguzik@gmail.com> apparmor: try to avoid refing the label in apparmor_file_open
If the label is not stale (which is the common case), the fact that the
passed file object holds a reference can be leverged to avoid the
ref/unref cycle. Doing so reduces performance impact of apparmor on
parallel open() invocations.
When benchmarking on a 24-core vm using will-it-scale's open1_process
("Separate file open"), the results are (ops/s):
before: 6092196
after: 8309726 (+36%)
Signed-off-by: Mateusz Guzik <mjguzik@gmail.com>
Signed-off-by: John Johansen <john.johansen@canonical.com>
|