On Sun, Mar 29, 2020 at 12:39:21PM +0200, Toke Høiland-Jørgensen wrote: > > > I guess all that is acceptable behavior to some libxdp users. > > I believe so. Not for us. Sadly that's where we part ways. we will not be using your libxdp. Existing xdp api was barely usable in the datacenter environment. replace_fd makes no difference. > exclusivity does come in handy. And as I said, I can live with there > being two APIs as long as there's a reasonable way to override the > bpf_link "lock" :) I explained many times already that bpf_link for XDP is NOT a second api to do the same thing. I understand that you think it's a second api, but when you keep repeating 'second api' it makes other folks (who also don't understand the difference) to make wrong conclusions that they can use either to achieve the same thing. They cannot. And it makes my job explaining harder. So please drop 'second api' narrative.
