From: Thiemo Seufer <ths@networkno.de>
To: Ely Soto <Soto.Ely@orbital.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] 0.9.0 Win32 Tap inferface PPC Guest issue
Date: Wed, 18 Apr 2007 00:22:41 +0100 [thread overview]
Message-ID: <20070417232240.GB5096@networkno.de> (raw)
In-Reply-To: <OF06417C40.5016D444-ON852572B8.006A8353-852572B8.006C4E6F@orbital.com>
Ely Soto wrote:
> Ok this is the fix I came up with.
>
> Basically it will check all the other objects that could potentially be
> waiting for service. This will prevent one high priority object from
> starving the rest.
>
> I'm not certain what the intention for the timeout > 0 check but this
> completely prevented any wait object servicing on my machine.
>
> The Tap interface now works smoothly without issue.
Please resend the version for current CVS as unified diff (diff -u)
without breaking the line formatting (an attachment should do).
Thiemo
next prev parent reply other threads:[~2007-04-17 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 18:50 [Qemu-devel] 0.9.0 Win32 Tap inferface PPC Guest issue Ely Soto
2007-04-05 19:30 ` Ely Soto
2007-04-05 21:01 ` Ely Soto
2007-04-09 17:51 ` Ely Soto
2007-04-09 19:42 ` Ely Soto
2007-04-17 23:22 ` Thiemo Seufer [this message]
2007-04-18 17:27 ` Ely Soto
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=20070417232240.GB5096@networkno.de \
--to=ths@networkno.de \
--cc=Soto.Ely@orbital.com \
--cc=qemu-devel@nongnu.org \
/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.