On 11.02.2019 17:15, Thomas Gleixner wrote:
> On Mon, 11 Feb 2019, Alexey Budankov wrote:
>> On 11.02.2019 1:34, Thomas Gleixner wrote:
>>> On Thu, 7 Feb 2019, Alexey Budankov wrote:
>>>
>>> General note: Please stay in the 80 char limit for all of the text.
>>
>> Yes, sure. [PATCH v2 4/4] implem
On Mon, 11 Feb 2019, Alexey Budankov wrote:
> On 11.02.2019 1:34, Thomas Gleixner wrote:
> > On Thu, 7 Feb 2019, Alexey Budankov wrote:
> >
> > General note: Please stay in the 80 char limit for all of the text.
>
> Yes, sure. [PATCH v2 4/4] implements wrapping at 72 columns.
So you provide crap
On 11.02.2019 1:34, Thomas Gleixner wrote:
> On Thu, 7 Feb 2019, Alexey Budankov wrote:
>
> General note: Please stay in the 80 char limit for all of the text.
Yes, sure. [PATCH v2 4/4] implements wrapping at 72 columns.
>
>> +The perf_events system call API [2]_ allocates file descriptors fo
On Thu, 7 Feb 2019, Alexey Budankov wrote:
General note: Please stay in the 80 char limit for all of the text.
> +The perf_events system call API [2]_ allocates file descriptors for every
> configured
> +PMU event. Open file descriptors are a per-process accountable resource
> governed
> +by th
Extend perf-security.rst file with perf_events/Perf resource control
section describing RLIMIT_NOFILE and perf_event_mlock_kb settings for
performance monitoring user processes.
Signed-off-by: Alexey Budankov
---
Changes in v2:
- applied comments on v1
---
Documentation/admin-guide/perf-secur
