Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20200727184506.2279656-1-guro@fb.com> <20200727184506.2279656-36-guro@fb.com>
In-Reply-To: <20200727184506.2279656-36-guro@fb.com>
From:   Andrii Nakryiko <andrii.nakryiko@gmail.com>
Date:   Mon, 27 Jul 2020 23:09:43 -0700
Message-ID: <CAEf4BzYUhybiSz2S-jtuv5+KcaHSxCLoY=nq1g597bvwpUemZw@mail.gmail.com>
Subject: Re: [PATCH bpf-next v2 35/35] perf: don't touch RLIMIT_MEMLOCK
To:     Roman Gushchin <guro@fb.com>,
        Arnaldo Carvalho de Melo <acme@kernel.org>
Cc:     bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
        Alexei Starovoitov <ast@kernel.org>,
        Daniel Borkmann <daniel@iogearbox.net>,
        Kernel Team <kernel-team@fb.com>,
        open list <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, Jul 27, 2020 at 12:21 PM Roman Gushchin <guro@fb.com> wrote:
>
> Since bpf stopped using memlock rlimit to limit the memory usage,
> there is no more reason for perf to alter its own limit.
>
> Signed-off-by: Roman Gushchin <guro@fb.com>
> ---

Cc'd Armaldo, but I'm guessing it's a similar situation that latest
perf might be running on older kernel and should keep working.

>  tools/perf/builtin-trace.c      | 10 ----------
>  tools/perf/tests/builtin-test.c |  6 ------
>  tools/perf/util/Build           |  1 -
>  tools/perf/util/rlimit.c        | 29 -----------------------------
>  tools/perf/util/rlimit.h        |  6 ------
>  5 files changed, 52 deletions(-)
>  delete mode 100644 tools/perf/util/rlimit.c
>  delete mode 100644 tools/perf/util/rlimit.h
>

[...]