linux-um archives
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Recent patches of note
Date: Thu, 16 Jun 2005 12:07:28 -0400	[thread overview]
Message-ID: <20050616160728.GA6040@ccure.user-mode-linux.org> (raw)

I'd like to call attention to some recent patches that may be of interest
to people before they hit mainline.  These are all on my incremental patches
page, http://user-mode-linux.sf.net/patches.html

First, sched-starve (http://user-mode-linux.sourceforge.net/work/current/2.6/2.6.12-rc6-mm1/patches/sched-starve)

This fixes a timer initialization botch which resulted in soft lockup
warnings in recent kernels, total non-responsiveness (i.e. nothing
else would be scheduled) under any workload which avoided idling the
kernel, and may be responsible for the load average >= 1 problem.

I don't see that last here for some reason, so I'd like some
confirmation (or not) that this patch fixes that.

Second, I implemented soft interrupts, which reimplements interrupt
enabling and disabling with a flag rather than with sigprocmask.  This
cuts down hugely on the number of system calls that UML makes,
resulting in a very noticable performance increase.  This patch, plus
the other system call reducing patches which immediately follow it,
speed up my kernel builds by 20-25%.  By far the largest piece of this
is softints, although skas-no-flush-kernel also is noticable.

I'd like people to check out softints, at least, and report any
problems.  It's running fine here, but interrupt handling is a
sensitive area, so I'd like to know people are running it without
problems before pushing it to mainline.

				Jeff


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
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:[~2005-06-16 16:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 16:07 Jeff Dike [this message]
2005-06-16 17:36 ` [uml-devel] Recent patches of note Bodo Stroesser
2005-06-16 17:47   ` Jeff Dike
2005-06-16 17:55     ` Bodo Stroesser
2005-06-16 18:02       ` Bodo Stroesser
2005-06-16 18:09       ` Blaisorblade
2005-06-16 18:31         ` Bodo Stroesser
2005-06-16 18:41           ` Blaisorblade
2005-06-16 18:40             ` Bodo Stroesser
2005-06-16 18:51               ` Blaisorblade
2005-06-16 22:23                 ` Jeff Dike
2005-06-17  9:09                   ` Bodo Stroesser
2005-06-17 18:36                   ` Blaisorblade
2005-06-17  0:35         ` Jeff Dike
2005-06-17 18:40           ` Blaisorblade
     [not found] <s2b18c1b.063@ORANGE.OUS.EDU>
2005-06-16 22:13 ` Jeff Dike
  -- strict thread matches above, loose matches on Subject: below --
2005-06-16 22:59 Anthony Brock
     [not found] <s2b1a1ed.010@ORANGE.OUS.EDU>
2005-06-20 14:47 ` Jeff Dike
     [not found] <s2b19c99.097@ORANGE.OUS.EDU>
2005-06-20 14:53 ` Jeff Dike
2005-06-20 17:59   ` William Stearns
2005-06-20 21:31     ` Blaisorblade
     [not found] <s2b6982e.048@ORANGE.OUS.EDU>
2005-06-20 20:11 ` Jeff Dike

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=20050616160728.GA6040@ccure.user-mode-linux.org \
    --to=jdike@addtoit.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