From: Jens Axboe <jaxboe@fusionio.com>
To: ren yufei <renyufei83@yahoo.com.cn>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: rdma ioengine
Date: Mon, 1 Aug 2011 10:03:21 +0200 [thread overview]
Message-ID: <4E365DC9.8040301@fusionio.com> (raw)
In-Reply-To: <4E365754.7030603@fusionio.com>
On 2011-08-01 09:35, Jens Axboe wrote:
> On 2011-08-01 03:47, ren yufei wrote:
>> Hi Jens,
>>
>> I have hacked an rdma ioengine based on OFED for fio which could test both rdma memory semantic (rdma_write/rdma_read) and channel semantic (send/recv). Would you like to merge this engine into fio?
>>
>> notes
>> 1) RDMA engine works in IB, iWarp and RoCE.
>> 2) RDMA engine is disable by default. To enable it, execute the following before compile:
>> $ export EXTFLAGS="-DFIO_HAVE_RDMA"
>> $ export EXTLIBS="-libverbs -lrdmacm"
>
> Exciting! I'd love to apply this, but somewhere along the way the patch
> has been white space damaged. Can you resend this patch gzip'ed or
> something like that, to ensure that it doesn't get modified along the
> way? Bonus points if you re-indent, fio uses real tabs and not 4 spaces.
> Not a huge problem, I'll just lindent it as-is if need be.
>
> It'd be great to have a small job file included as well for testing, and
> an example of a result using that job file.
And you already did include example job files, excellent. I applied your
patch, the mangling wasn't too bad. I also re-indented it with indent,
so it conforms to the fio coding style. Please double check the result!
Thanks.
--
Jens Axboe
next prev parent reply other threads:[~2011-08-01 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 1:47 rdma ioengine ren yufei
2011-08-01 7:35 ` Jens Axboe
2011-08-01 8:03 ` Jens Axboe [this message]
2011-08-01 17:02 ` ren yufei
-- strict thread matches above, loose matches on Subject: below --
2011-08-01 18:56 Yufei Ren
2011-08-01 19:59 ` 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=4E365DC9.8040301@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=fio@vger.kernel.org \
--cc=renyufei83@yahoo.com.cn \
/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.