Re: Accessing userspace created persistent eBPF maps from kernel bpf restricted C
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: Accessing userspace created persistent eBPF maps from kernel bpf restricted C
- From: David Miller <davem@xxxxxxxxxxxxx>
- Date: Thu, 07 Sep 2017 19:12:16 -0700 (PDT)
- In-reply-to: <CABUc5FHPNjdauR-0OuK=P=Uvx81puBZ+cjnX6sMXDZQguCaAiw@mail.gmail.com>
- References: <CABUc5FF3Lx=7ECCT_bzxcbKHkXX1Vs66KJHabJExqTJ8Bz0VgA@mail.gmail.com> <CAC1LvL0kQqKJtqo-ea1qonvKVbKaUkhk=QUSBZCVhmoC+tbCZQ@mail.gmail.com> <CABUc5FHPNjdauR-0OuK=P=Uvx81puBZ+cjnX6sMXDZQguCaAiw@mail.gmail.com>
From: Kiran T <kiran.lkml@xxxxxxxxx>
Date: Thu, 7 Sep 2017 17:46:47 -0700
> If maps can be made persistent from userspace, but the kernel side
> bpf can't quite access it, it doesn't make much sense :(
Pinning is so that an unload of a BPF program doesn't cause it's maps
to go away.
It's designed so that things like statistics can be persistent across
BPF program loads.
So you can load and unload a BPF program multiple times, and you won't
lose the statistic increments done by earlier instances.
[Index of Archives]
[Linux Networking Development]
[Fedora Linux Users]
[Linux SCTP]
[DCCP]
[Gimp]
[Yosemite Campsites]