Re: [PATCH v2 0/8] irqbypass: Cleanups and a perf improvement

2025-06-25 Thread Sean Christopherson
On Fri, 16 May 2025 16:07:26 -0700, Sean Christopherson wrote: > The two primary goals of this series are to make the irqbypass concept > easier to understand, and to address the terrible performance that can > result from using a list to track connections. > > For the first goal, track the produc

Re: [PATCH v2 0/8] irqbypass: Cleanups and a perf improvement

2025-06-02 Thread Sean Christopherson
On Mon, Jun 02, 2025, Alex Williamson wrote: > On Fri, 16 May 2025 16:07:26 -0700 > Sean Christopherson wrote: > > > The two primary goals of this series are to make the irqbypass concept > > easier to understand, and to address the terrible performance that can > > result from using a list to tr

Re: [PATCH v2 0/8] irqbypass: Cleanups and a perf improvement

2025-06-02 Thread Alex Williamson
On Fri, 16 May 2025 16:07:26 -0700 Sean Christopherson wrote: > The two primary goals of this series are to make the irqbypass concept > easier to understand, and to address the terrible performance that can > result from using a list to track connections. > > For the first goal, track the produ

Re: [PATCH v2 0/8] irqbypass: Cleanups and a perf improvement

2025-05-18 Thread Michael S. Tsirkin
On Fri, May 16, 2025 at 04:07:26PM -0700, Sean Christopherson wrote: > The two primary goals of this series are to make the irqbypass concept > easier to understand, and to address the terrible performance that can > result from using a list to track connections. > > For the first goal, track the

[PATCH v2 0/8] irqbypass: Cleanups and a perf improvement

2025-05-16 Thread Sean Christopherson
The two primary goals of this series are to make the irqbypass concept easier to understand, and to address the terrible performance that can result from using a list to track connections. For the first goal, track the producer/consumer "tokens" as eventfd context pointers instead of opaque "void