From: David Ahern <dsahern@gmail.com>
To: Ben Greear <greearb@candelatech.com>, netdev <netdev@vger.kernel.org>
Subject: Re: VRF and/or cgroups problem on Fedora-30, 5.2.21+ kernel
Date: Fri, 22 Nov 2019 17:17:48 -0700 [thread overview]
Message-ID: <8ae551e1-5c2e-6a95-b4d1-3301c5173171@gmail.com> (raw)
In-Reply-To: <213aa1d3-5df9-0337-c583-34f3de5f1582@candelatech.com>
On 11/22/19 5:14 PM, Ben Greear wrote:
> On 11/22/19 4:06 PM, David Ahern wrote:
>> On 11/22/19 5:03 PM, Ben Greear wrote:
>>> Hello,
>>>
>>> We see a problem on a particular system when trying to run 'ip vrf exec
>>> _vrf1 ping 1.1.1.1'.
>>> This system reproduces the problem all the time, but other systems with
>>> exact same (as far as
>>> we can tell) software may fail occasionally, but then it will work
>>> again.
>>>
>>> Here is an strace output. I changed to the
>>> "/sys/fs/cgroup/unified/user.slice/user-1000.slice/session-2.scope/vrf/_vrf1"
>>>
>>>
>>> directory as root user, and could view the files in that directory, so
>>> I'm not sure why the strace shows error 5.
>>>
>>> Any idea what could be the problem and/or how to fix it or debug
>>> further?
>>>
>>>
>>> This command was run as root user.
>>
>> check 'ulimit -l'. BPF is used to set the VRF and it requires locked
>> memory.
>
> It is set to '64'. What is a good value to use?
>
This is a pain point in using BPF for this. It's really use case
dependent. 128kB, 256kB.
next prev parent reply other threads:[~2019-11-23 0:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 0:03 VRF and/or cgroups problem on Fedora-30, 5.2.21+ kernel Ben Greear
2019-11-23 0:06 ` David Ahern
2019-11-23 0:14 ` Ben Greear
2019-11-23 0:17 ` David Ahern [this message]
2019-11-23 0:23 ` Ben Greear
2019-11-23 18:10 ` David Ahern
2019-11-25 17:35 ` Ben Greear
2019-11-25 20:53 ` David Ahern
2019-11-26 8:48 ` Toke Høiland-Jørgensen
2019-11-26 17:36 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ae551e1-5c2e-6a95-b4d1-3301c5173171@gmail.com \
--to=dsahern@gmail.com \
--cc=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).