Re: [RFC 0/8] ioring: network driver

2024-12-20 Thread Stephen Hemminger
On Fri, 20 Dec 2024 14:34:27 + Konstantin Ananyev wrote: > > > From: Konstantin Ananyev [mailto:konstantin.anan...@huawei.com] > > > > > > > > > This is first draft of new simplified TAP device that uses > > > > > > the Linux kernel ioring API to provide a read/write ring > > > > > > with k

RE: [RFC 0/8] ioring: network driver

2024-12-20 Thread Konstantin Ananyev
> > From: Konstantin Ananyev [mailto:konstantin.anan...@huawei.com] > > > > > > > This is first draft of new simplified TAP device that uses > > > > > the Linux kernel ioring API to provide a read/write ring > > > > > with kernel. > > > > > > > > > > This is split from tap device because there a

RE: [RFC 0/8] ioring: network driver

2024-12-19 Thread Morten Brørup
> From: Konstantin Ananyev [mailto:konstantin.anan...@huawei.com] > > > > > This is first draft of new simplified TAP device that uses > > > > the Linux kernel ioring API to provide a read/write ring > > > > with kernel. > > > > > > > > This is split from tap device because there are so many > > >

RE: [RFC 0/8] ioring: network driver

2024-12-12 Thread Konstantin Ananyev
> > > This is first draft of new simplified TAP device that uses > > > the Linux kernel ioring API to provide a read/write ring > > > with kernel. > > > > > > This is split from tap device because there are so many > > > unnecessary things in existing tap, and supporting ioring is > > > better wi

Re: [RFC 0/8] ioring: network driver

2024-12-11 Thread Stephen Hemminger
On Wed, 11 Dec 2024 11:34:39 + Konstantin Ananyev wrote: > > This is first draft of new simplified TAP device that uses > > the Linux kernel ioring API to provide a read/write ring > > with kernel. > > > > This is split from tap device because there are so many > > unnecessary things in exis

RE: [RFC 0/8] ioring: network driver

2024-12-11 Thread Konstantin Ananyev
> This is first draft of new simplified TAP device that uses > the Linux kernel ioring API to provide a read/write ring > with kernel. > > This is split from tap device because there are so many > unnecessary things in existing tap, and supporting ioring is > better without ifdefs etc. The defa