linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Anton Ivanov <aivanov@Brocade.com>
To: "user-mode-linux-devel@lists.sourceforge.net"
	<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] [PATCH] Missing includes in start up
Date: Sun, 8 Nov 2015 22:43:48 +0000	[thread overview]
Message-ID: <563FD01A.3060102@brocade.com> (raw)
In-Reply-To: <CAFLxGvyCpg3yiYdxZYXBn+GwYTjSECK1bxxQinRFQDQk0j4gSw@mail.gmail.com>

No worries.

A completely rewritten IRQ controller patch is coming in ~ 15 minutes  
or so. 20% gain across the board for a basic config, up to 100s% gain if 
you register large numbers of devices (in the tens).

Just finishing to run it through its paces :)

It is also a pre-requisite to do multipacket reads/multipacket writes 
which will be next.

A.


On 08/11/15 22:38, Richard Weinberger wrote:
> On Sun, Nov 8, 2015 at 4:18 PM, Anton Ivanov <aivanov@brocade.com> wrote:
>> Hi Richard,
>>
>> This is vs your tree, 4.x master branch in linus repo actually has
>> sys/resource.h
>>
>> Pls ignore the patch.
> Sorry for the trouble!
> I forgot to mention that linux-next is the only valid branch in my tree.
> As UML does not have much patch flood I test them locally and push them directly
> to linux-next.
>

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


      reply	other threads:[~2015-11-08 22:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-08 14:58 [uml-devel] [PATCH] Missing includes in start up Anton Ivanov
2015-11-08 15:18 ` Anton Ivanov
2015-11-08 22:38   ` Richard Weinberger
2015-11-08 22:43     ` Anton Ivanov [this message]

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=563FD01A.3060102@brocade.com \
    --to=aivanov@brocade.com \
    --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;
as well as URLs for NNTP newsgroup(s).