From: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH v2] EPOLL Interrupt Controller V2.0
Date: Tue, 10 Nov 2015 18:42:17 +0000 [thread overview]
Message-ID: <56423A89.2040206@kot-begemot.co.uk> (raw)
In-Reply-To: <5640B5B5.7050907@kot-begemot.co.uk>
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 <aivanov@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
next prev parent reply other threads:[~2015-11-10 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 14:33 [uml-devel] [PATCH v2] EPOLL Interrupt Controller V2.0 Anton Ivanov
2015-11-09 15:03 ` Anton Ivanov
2015-11-10 18:42 ` Anton Ivanov [this message]
2015-11-10 20:24 ` Richard Weinberger
2015-11-11 20:46 ` Thomas Meyer
2015-11-11 21:05 ` Richard Weinberger
2015-11-11 21:39 ` Anton Ivanov
2015-11-11 21:49 ` stian
2015-11-11 23:25 ` Anton Ivanov
2015-11-12 12:29 ` Anton Ivanov
2015-11-12 15:23 ` Anton Ivanov
2015-11-12 16:03 ` Anton Ivanov
2015-11-16 8:09 ` Anton Ivanov
2015-11-18 8:33 ` Anton Ivanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56423A89.2040206@kot-begemot.co.uk \
--to=anton.ivanov@kot-begemot.co.uk \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox