On 12/02/2017 12:08 AM, Jakub Kicinski wrote: > Hi! > > The purpose of this series is to add a software model of BPF offloads > to make it easier for everyone to test them and make some of the more > arcane rules and assumptions more clear. > > The series starts with 3 patches aiming to make XDP handling in the > drivers less error prone. Currently driver authors have to remember > to free XDP programs if XDP is active during unregister. With this > series the core will disable XDP on its own. It will take place > after close, drivers are not expected to perform reconfiguration > when disabling XDP on a downed device. > > Next two patches add the software netdev driver, followed by a python > test which exercises all the corner cases which came to my mind. > > Test needs to be run as root. It will print basic information to > stdout, but can also create a more detailed log of all commands > when --log option is passed. Log is in Emacs Org-mode format. > > ./tools/testing/selftests/bpf/test_offload.py --log /tmp/log > > Last two patches replace the SR-IOV API implementation of dummy. > > v3: > - move the freeing of vfs to release (Phil). > v2: > - free device from the release function; > - use bus-based name generatin instead of netdev name. > v1: > - replace the SR-IOV API implementation of dummy; > - make the dev_xdp_uninstall() also handle the XDP generic (Daniel).
Series applied to bpf-next, thanks Jakub!
