From: Jan Kiszka <jan.kiszka@siemens.com>
To: liu ping fan <qemulist@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] slirp: fill mainloop timeout with more precise value
Date: Tue, 13 Aug 2013 10:29:18 +0200 [thread overview]
Message-ID: <5209EE5E.5020100@siemens.com> (raw)
In-Reply-To: <CAJnKYQmK1geqDL5OR7r2Vyk2Fi9by4dY1m6JHDj1cSBB54-jOQ@mail.gmail.com>
On 2013-08-13 10:25, liu ping fan wrote:
> On Tue, Aug 13, 2013 at 4:19 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> On 2013-08-13 05:15, Liu Ping Fan wrote:
>>> If slirp needs to emulate tcp timeout, then the timeout value
>>> for mainloop should be more precise, which is determined by
>>> slirp's fasttimo or slowtimo.
>>>
>>> Signed-off-by: Liu Ping Fan <pingfank@linux.vnet.ibm.com>
>>> ---
>>> main-loop.c | 2 +-
>>> slirp/slirp.c | 18 ++++++++++++++++++
>>> 2 files changed, 19 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/main-loop.c b/main-loop.c
>>> index a44fff6..04120d2 100644
>>> --- a/main-loop.c
>>> +++ b/main-loop.c
>>> @@ -458,8 +458,8 @@ int main_loop_wait(int nonblocking)
>>> g_array_set_size(gpollfds, 0); /* reset for new iteration */
>>> /* XXX: separate device handlers from system ones */
>>> #ifdef CONFIG_SLIRP
>>> - slirp_update_timeout(&timeout);
>>> slirp_pollfds_fill(gpollfds);
>>> + slirp_update_timeout(&timeout);
>>
>> Why this reordering?
>>
> In order to give timeout more precise value, which is based on the
> result of fasttimo or slowtimo after slirp_pollfds_fill()
OK. But to avoid that the caller has to know this dependency, better
merge the update timeout logic into pollfds_fill.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-08-13 8:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 3:15 [Qemu-devel] [PATCH 0/3] slirp: fill mainloop with more precise timeout value Liu Ping Fan
2013-08-13 3:15 ` [Qemu-devel] [PATCH 1/3] slirp: make timeout local Liu Ping Fan
2013-08-13 8:03 ` Jan Kiszka
2013-08-13 8:30 ` liu ping fan
2013-08-13 3:15 ` [Qemu-devel] [PATCH 2/3] slirp: define timeout as macro Liu Ping Fan
2013-08-13 8:04 ` Jan Kiszka
2013-08-13 3:15 ` [Qemu-devel] [PATCH 3/3] slirp: fill mainloop timeout with more precise value Liu Ping Fan
2013-08-13 8:19 ` Jan Kiszka
2013-08-13 8:25 ` liu ping fan
2013-08-13 8:29 ` Jan Kiszka [this message]
2013-08-13 8:33 ` liu ping fan
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=5209EE5E.5020100@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemulist@gmail.com \
--cc=stefanha@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).