From: "roland" <for_spam@gmx.de>
To: "Christopher S. Aker" <caker@theshore.net>,
Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] Re: 2.6.9-bb3 creates zombie threads in SKAS
Date: Tue, 23 Nov 2004 00:56:07 +0100 [thread overview]
Message-ID: <050101c4d0ee$d68041a0$2000000a@schlepptopp> (raw)
In-Reply-To: 002d01c4d0eb$9d829810$0201a8c0@hawk
Hi Christopher,
> > Btw, question: what about your I/O token limiter? Actively using it? Could
> > start being worked on for merge (there is at least one bug-report on it by
> > "roland" on a strange but valid test-case).
see http://sourceforge.net/mailarchive/message.php?msg_id=8560363
that`s probably just a minor one.
roland
----- Original Message -----
From: "Christopher S. Aker" <caker@theshore.net>
To: "Blaisorblade" <blaisorblade_spam@yahoo.it>
Cc: <user-mode-linux-devel@lists.sourceforge.net>; "Bodo Stroesser" <bstroesser@fujitsu-siemens.com>
Sent: Tuesday, November 23, 2004 12:33 AM
Subject: [uml-devel] Re: 2.6.9-bb3 creates zombie threads in SKAS
> > On Monday 22 November 2004 23:23, Christopher S. Aker wrote:
> > > Hello,
> > Btw, question: what about your I/O token limiter? Actively using it? Could
> > start being worked on for merge (there is at least one bug-report on it by
> > "roland" on a strange but valid test-case).
>
> Yes, I use it in all my kernels -- it's invaluable.to me for stopping swap-thrashing
> UMLs from taking down the entire host. What bug did Roland find? If you want to
> merge it, you probably want to add some way to turn it off completely (perhaps by
> default). I'm sure there are other improvements to be made...
>
> > > I thought I'd give 2.6.9-bb3 a shot, and I had a bunch of users report the
> > > accumulation of zombies.
> > What the hell! This should *not* happen. What did we (I mean developers) do?
> > > This is on a 2.6.7 host, using your
> > > host-skas3-2.6.7-v1 patch.
> > ??? There is a ton of bugs in that patch (see the changelogs on my site).
> > Actually, it's likely you're not going to be hurt by them if you're using
> > NPTL on the host (it is *hard* to get them in that case), but you'd better
> > upgrade.
>
> No doubt... I've been getting ready for The Great Reboot (38 hosts), but it takes
> careful planning with that many hosts. I've been testing a SKAS-V7 based host kernel
> and things look very good. All the weird bugs have gone away (mysql instability,
> Gentoo not able to complete emerges, this is all on either V1 or V6 skas patches).
> Looking forward to the upgrade to V7, and the latest CFQ changes.
>
> > I have been releasing tons of updates, and even too quickly (most times I was
> > not introducing new bugs, just fixing the ones I and Bodo Stroesser was
> > finding) but -V1 is "a bit" old. That said, this should not happen.
>
> Changes have been coming so quickly, it's hard to keep up :)
>
> > > I'm not sure if it happened on newer host
> > > kernels, since I had to revert it back quickly.
> >
> > Back to what? To 2.6.9-bb2 or to 2.6.9?
>
> Vanilla 2.6.9-um
>
> > I'll check in these days what's going on... it was hyper-tested on 2.6.9 host
> > (not by me, but I trust Bodo Stroesser normally), but not on other hosts, I
> > guess.
>
> Thanks,
> -Chris
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> User-mode-linux-devel mailing list
> User-mode-linux-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.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:[~2004-11-22 23:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000901c4d0e1$e7f998d0$0201a8c0@hawk>
2004-11-22 22:46 ` [uml-devel] Re: 2.6.9-bb3 creates zombie threads in SKAS Blaisorblade
2004-11-22 23:33 ` Christopher S. Aker
2004-11-22 23:56 ` roland [this message]
2004-11-23 7:28 ` [uml-devel] Updated token-limiter patch, was " Christopher S. Aker
2004-11-23 20:10 ` Blaisorblade
2004-11-23 14:48 ` [uml-devel] " Bodo Stroesser
2004-11-23 17:49 ` Christopher S. Aker
2004-11-23 17:53 ` dopez
2004-11-23 19:30 ` Blaisorblade
2004-11-23 18:22 ` Blaisorblade
2004-11-23 18:29 ` Christopher S. Aker
2004-11-30 18:55 ` Christopher S. Aker
2004-11-30 19:23 ` Bodo Stroesser
2004-11-30 20:59 ` Christopher S. Aker
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='050101c4d0ee$d68041a0$2000000a@schlepptopp' \
--to=for_spam@gmx.de \
--cc=blaisorblade_spam@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=caker@theshore.net \
--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