linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: "Christopher S. Aker" <caker@theshore.net>,
	roland <for_spam@gmx.de>,
	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 21:10:24 +0100	[thread overview]
Message-ID: <200411232110.24634.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <007f01c4d12e$05d6f1d0$0201a8c0@hawk>

On Tuesday 23 November 2004 08:28, Christopher S. Aker wrote:
> > > > 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".

> I see.  nanosleep doesn't accept an tv_nsec value over 999  999  999, 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

Ok, seen that - to be cleaner, I'll change when I remember this to set, 
instead, tv_sec to 1 (tv_nsec cannot be one billion because one billion of 
nsec is one sec). I see that there is no actual difference and that doing 
this is a bit more invasive, so I guess that you fixed it this way on 
purpose, but, for merging, such things deserve cleaning. Also the proc status 
will have to be moved to a uml-only file.

Just a little thing, anyway - the patch is very nice.
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade


-------------------------------------------------------
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

  reply	other threads:[~2004-11-23 20:09 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       ` [uml-devel] Updated token-limiter patch, was " Christopher S. Aker
2004-11-23 20:10         ` Blaisorblade [this message]
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=200411232110.24634.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.com \
    --cc=caker@theshore.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox