From: "Christopher S. Aker" <caker@theshore.net>
To: roland <for_spam@gmx.de>, Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] Updated token-limiter patch, was 2.6.9-bb3 creates zombie threads in SKAS
Date: Tue, 23 Nov 2004 01:28:23 -0600 [thread overview]
Message-ID: <007f01c4d12e$05d6f1d0$0201a8c0@hawk> (raw)
In-Reply-To: 050101c4d0ee$d68041a0$2000000a@schlepptopp
> > > 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
From that post:
> ps:
> the token limiter seems to have a little bug:
> set token_refill=1
> do a "dd if=/dev/zero of=test.dat bs=1024k count=whatever"
> then "sync".
> for me, io isn`t limited here - io_tokens just becomes negative - nothing more.
> ok - io_refill=1 is no "real world" value anyway - so not really important to be
fixed - but interesting :)
I see. nanosleep doesn't accept an tv_nsec value over 999999999, so there's a simple
fix in this patch:
http://www.theshore.net/~caker/uml/patches/token-limiter-v2.patch
This patch also includes the proc-io_status patch. It's against 2.6.9, but applies
to 2.4-um as well.
-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
next prev parent reply other threads:[~2004-11-23 7:21 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
2004-11-23 7:28 ` Christopher S. Aker [this message]
2004-11-23 20:10 ` [uml-devel] Updated token-limiter patch, was " 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='007f01c4d12e$05d6f1d0$0201a8c0@hawk' \
--to=caker@theshore.net \
--cc=blaisorblade_spam@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=for_spam@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.