All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yufei Ren <yufei.ren@stonybrook.edu>
To: Jens Axboe <axboe@kernel.dk>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH 3/4] rdma ioengine improvement
Date: Mon, 22 Oct 2012 14:39:04 -0400	[thread overview]
Message-ID: <CAG5pYQdJ8oZZhazrJEED+zu9bR4zJ6h_G=wTnG3MF0mJeDgegQ@mail.gmail.com> (raw)
In-Reply-To: <5084FE8B.6090608@kernel.dk>

On Mon, Oct 22, 2012 at 4:06 AM, Jens Axboe <axboe@kernel.dk> wrote:
> On 2012-10-20 05:11, Yufei Ren wrote:
>> From: Yufei Ren <renyufei83@gmail.com>
>
> This one needs a bit of explaining. What is the point of using a
> re-entrant variant of rand(), if you are using a shared static variable
> anyway?
>

It's my buggy :-)

> Would it be better to use the fio shipped rand, now we're in there
> anyway?
>

Thanks for remind me the fio shipped rand. Let me send you another patch.

>> @@ -790,6 +792,13 @@ static int fio_rdmaio_connect(struct thread_data *td, struct fio_file *f)
>>       /* wait for remote MR info from server side */
>>       rdma_poll_wait(td, IBV_WC_RECV);
>>
>> +     /* In SEND/RECV test, iodepth in RECV side is deeper
>> +      * in SEND side. RECV needs more time to construct the
>> +      * buffer blocks, so the server side may need to stop
                                                   ~~~~~~~~~ should be SEND side
>> +      * some time before transfer data.
>> +      */
>> +     usleep(500000);
>> +
>>       return 0;
>
> Hmm?

After rdma connection(queue pair) established, data source and data
sink commit data blocks into send queue and receive queue,
respectively. If data source posts so many io requests that over the
capacity of the receiver queue. Receiver Not Ready (RNR) error comes
out. To avoid this, it's better that data source waits for some time
until data sink posts sufficient number of recv buffers into recv
queue.

Maybe it is a better way to add a `receiver ready notification' from
the sink to the source for addressing this problem.

Anyway, I will send you another patch with clear comments.

>
> --
> Jens Axboe
>


  reply	other threads:[~2012-10-22 18:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20  3:11 [PATCH 0/4] FIO libnuma integration and 3 patches Yufei Ren
2012-10-20  3:11 ` [PATCH 1/4] cpuio engine cpuload bug fix Yufei Ren
2012-10-22  8:03   ` Jens Axboe
2012-10-20  3:11 ` [PATCH 2/4] thread cpu resource statistics " Yufei Ren
2012-10-22  8:04   ` Jens Axboe
2012-10-22 16:33     ` Yufei Ren
2012-10-22 17:10       ` Jens Axboe
2012-10-20  3:11 ` [PATCH 3/4] rdma ioengine improvement Yufei Ren
2012-10-22  8:06   ` Jens Axboe
2012-10-22 18:39     ` Yufei Ren [this message]
2012-10-20  3:11 ` [PATCH 4/4] Fine-grained job level numa control Yufei Ren
2012-10-22  8:07   ` Jens Axboe

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='CAG5pYQdJ8oZZhazrJEED+zu9bR4zJ6h_G=wTnG3MF0mJeDgegQ@mail.gmail.com' \
    --to=yufei.ren@stonybrook.edu \
    --cc=axboe@kernel.dk \
    --cc=fio@vger.kernel.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.