[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180214020443.oox4tokpio2jqmkp@ast-mbp.dhcp.thefacebook.com>
Date: Tue, 13 Feb 2018 18:04:45 -0800
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Yonghong Song <yhs@...com>
Cc: ast@...com, daniel@...earbox.net, netdev@...r.kernel.org,
brakmo@...com, kernel-team@...com
Subject: Re: [PATCH bpf-next] tools/bpf: adjust rlimit RLIMIT_MEMLOCK for
test_tcpbpf_user
On Tue, Feb 13, 2018 at 10:35:05AM -0800, Yonghong Song wrote:
> The default rlimit RLIMIT_MEMLOCK is 64KB. In certain cases,
> e.g. in a test machine mimicking our production system, this test may
> fail due to unable to charge the required memory for map creation:
> # ./test_tcpbpf_user
> libbpf: failed to create map (name: 'global_map'): Operation not permitted
> libbpf: failed to load object 'test_tcpbpf_kern.o'
> FAILED: load_bpf_file failed for: test_tcpbpf_kern.o
>
> Changing the default rlimit RLIMIT_MEMLOCK to unlimited makes
> the test always pass.
>
> Signed-off-by: Yonghong Song <yhs@...com>
Applied to bpf-next, Thanks Yonghong.
Powered by blists - more mailing lists