qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, stefanha@redhat.com,
	ronniesahlberg@gmail.com
Subject: Re: [Qemu-devel] [PATCH] block/iscsi: handle BUSY condition
Date: Thu, 05 Jun 2014 11:29:12 +0200	[thread overview]
Message-ID: <53903868.6070500@kamp.de> (raw)
In-Reply-To: <538849D8.10806@redhat.com>

On 30.05.2014 11:05, Paolo Bonzini wrote:
> Il 30/05/2014 11:04, Peter Lieven ha scritto:
>> Am 30.05.2014 07:50, schrieb Paolo Bonzini:
>>> Il 29/05/2014 22:25, Peter Lieven ha scritto:
>>>> Am 29.05.2014 21:17, schrieb Paolo Bonzini:
>>>>> Il 29/05/2014 20:41, Peter Lieven ha scritto:
>>>>>> static inline unsigned geo_rand_range(double m, double n) {
>>>>>>     return exp((log(m) + (double)rand() /
>>>>>>                (RAND_MAX / (log(n) - log(m) + log(1)) + log(1))));
>>>>>> }
>>>>>
>>>>> Yes, exactly (except that log(1) is zero, and was only needed in your case because you were using integers).
>>>>
>>>> Regarding aio_timer_new vs. aio_timer_init. Shall we really have the complete QEMU_TIMER struct in each
>>>> iTask? We need this retry_timer only in the really rare case of a BUSY.
>>>
>>> Ok, makes sense.  Though the overall cost of IscsiTasks should be less than 4k per block device with a separate QemuTimer, and 8k if you embed it.
>>>
>>> Otherwise the patch looks good, thanks!
>>
>> Okay, when are you preparing the next pull request?
>
> After the dataplane patches go in.  But you can send the patch now, I'll rebase.

It might be that we need a LIBS+= -lm to the Makefile in the root directory. I had strange problems when linking qemu-img/qemu-io/qemu-nbd.

Peter

       reply	other threads:[~2014-06-05  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1401384704-14103-1-git-send-email-pl@kamp.de>
     [not found] ` <538772C9.8080500@redhat.com>
     [not found]   ` <53877F41.7090805@kamp.de>
     [not found]     ` <538787DC.10306@redhat.com>
     [not found]       ` <5387979F.1070103@kamp.de>
     [not found]         ` <53881C32.2040703@redhat.com>
     [not found]           ` <5388498C.9040007@kamp.de>
     [not found]             ` <538849D8.10806@redhat.com>
2014-06-05  9:29               ` Peter Lieven [this message]
2014-06-05  9:44                 ` [Qemu-devel] [PATCH] block/iscsi: handle BUSY condition Paolo Bonzini
2014-06-05 10:13                   ` Peter Lieven
2014-06-06 12:33 George-Cristian Bîrzan

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=53903868.6070500@kamp.de \
    --to=pl@kamp.de \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@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).