On Sun, May 15, 2022 at 01:47:11PM +0300, Yaşar Arabacı wrote: > Currently this driver uses ioctl for reading/writing per-device and > per-client configuration. Per-client configuration can be handled by > usespace and sent to driver with each write() call. Doing so does not > introduce extra overhead because we copy tx config to fifo for each > transmit anyway. This way, we don't have to introduce new ioctl's. Wait, you just changed the user api of the write/read call to the driver? That's dangerous, especially: > This has not been tested as I don't have access to hardware. That's not good. You need to figure out what userspace tool(s) use this api and ensure that you did not just break them for no good reason. thanks, greg k-h
