Thomas Mayer found a couple of issues which crept up when porting v1 to 
the newer kernels.

It also crashes with his config - I am analyzing the differences between 
that and mine to find the culrpit.

Once I have fixed both I will resubmit v3. So for now this is just 
"subject for discussion", do not use yet.

A

On 09/11/15 15:03, Anton Ivanov wrote:
> It throws a couple of harmless "epoll del fd" warnings on reboot which 
> result the fact that disable_fd/enable_fd are not removed in the 
> terminal/line code.
>
> These are harmless and will go away once the term/line code gets 
> support for real write IRQs in addition to read at some point in the 
> future.
>
> I have fixed the file descriptor leak in the reboot case.
>
> A.
>
> On 09/11/15 14:33, Anton Ivanov wrote:
>> Epoll based interrupt controller.
>>
>> IMPROVES: IO loop performance - no per fd lookups, allowing for
>> 15% IO speedup in minimal config going to 100s of % with many
>> devices - a N^N lookup is now replaced by a log(N)
>>
>> ADDS: True Write IRQ functionality
>>
>> OBSOLETES: The need to call reactivate_fd() in any driver which
>> has only read IRQ semantics. Write IRQs work, but will need to
>> be updated to use this fully.
>>
>> Potentially (with a change in API) will allow both edge and level
>> IRQ semantics.
>>
>> Pre-requisite for using packet mmap and multipacket read/write
>> which do not get along with poll() very well.
>>
>> Signed-off-by: Anton Ivanov <aiva...@brocade.com>
>


------------------------------------------------------------------------------
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

Reply via email to