From: Bart Van Assche <bvanassche@acm.org>
To: linux-scsi <linux-scsi@vger.kernel.org>
Cc: Hannes Reinecke <hare@suse.de>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Alexander Graf <alex@csgraf.de>,
Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [PATCH 0/3] ibmvscsis driver rewrite
Date: Thu, 10 Feb 2011 22:22:04 +0100 [thread overview]
Message-ID: <AANLkTikN4dRuAXg26LrPa65WpWfBG1CHwmctGOGwmFWE@mail.gmail.com> (raw)
In-Reply-To: <1297363312.18212.153.camel@haakon2.linux-iscsi.org>
On Thu, Feb 10, 2011 at 7:41 PM, Nicholas A. Bellinger
<nab@linux-iscsi.org> wrote:
>
> On Thu, 2011-02-10 at 13:48 +0100, Hannes Reinecke wrote:
> >
> > On 02/10/2011 01:21 PM, FUJITA Tomonori wrote:
> > > Finally, I have the working driver. We are ready to remove the old
> > > ibmvstgt driver.
> > >
> > Hmm. Wouldn't it be possible to use it as a template for a
> > virtio-srp target?
> > From what I've seen we 'just' need to modify it to use virtio
> > instead for pSeries rdma callbacks.
> > And then we would have a virtio-srp target onto which any kvm guests
> > could connect to.
One should keep in mind that there exist two kinds of SRP drivers for Linux:
- Those based on synchronous data transfer calls - calls that only
return after the entire transfer has finished. The ibmvscsi, ibmvscsis
drivers and the libsrp library fall in this category.
- Those based on asynchronous data transfers - calls that return
immediately and where a callback function is invoked to report
completion. ib_srp and ib_srpt fall into this category (ib_srp is
upstream, ib_srpt not yet).
As far as I know the virtio interface uses callbacks and hence is an
asynchronous interface ? If so, the InfiniBand drivers might be a
better starting point.
Bart.
prev parent reply other threads:[~2011-02-10 21:22 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 12:21 [PATCH 0/3] ibmvscsis driver rewrite FUJITA Tomonori
2011-02-10 12:21 ` [PATCH 1/3] libsrp: add srp_data_length helper function FUJITA Tomonori
2011-02-10 12:21 ` [PATCH 2/3] libsrp: fix dma_unmap_sg FUJITA Tomonori
2011-02-10 12:21 ` [PATCH 3/3] tcm ibmvscsis driver FUJITA Tomonori
2011-02-10 19:03 ` Nicholas A. Bellinger
2011-02-14 1:36 ` FUJITA Tomonori
2011-02-14 3:26 ` FUJITA Tomonori
2011-02-14 9:01 ` Nicholas A. Bellinger
2011-02-14 9:29 ` FUJITA Tomonori
2011-02-14 9:27 ` Nicholas A. Bellinger
2011-02-14 9:46 ` FUJITA Tomonori
2011-02-14 9:51 ` Nicholas A. Bellinger
2011-02-10 19:15 ` Brian King
2011-02-10 19:38 ` Nicholas A. Bellinger
2011-02-11 21:13 ` Brian King
2011-02-12 20:27 ` James Bottomley
2011-03-07 4:41 ` FUJITA Tomonori
2011-03-07 6:17 ` Nicholas A. Bellinger
2011-03-07 6:24 ` FUJITA Tomonori
2011-03-07 6:55 ` Nicholas A. Bellinger
2011-03-07 14:40 ` James Bottomley
2011-03-18 16:57 ` James Bottomley
2011-03-18 20:58 ` Brian King
2011-03-18 22:09 ` Nicholas A. Bellinger
2011-03-19 14:32 ` James Bottomley
2011-03-21 1:09 ` FUJITA Tomonori
2011-03-21 12:56 ` Brian King
2011-03-21 21:01 ` Brian King
2011-03-21 21:01 ` Nicholas A. Bellinger
2011-03-21 21:24 ` Brian King
2011-03-21 22:29 ` Nicholas A. Bellinger
2011-03-21 23:20 ` FUJITA Tomonori
2011-03-21 23:50 ` Nicholas A. Bellinger
2011-03-21 23:55 ` FUJITA Tomonori
2011-03-22 0:26 ` Nicholas A. Bellinger
2011-03-22 0:32 ` FUJITA Tomonori
2011-03-22 2:28 ` Nicholas A. Bellinger
2011-03-22 3:26 ` FUJITA Tomonori
2011-03-21 21:05 ` James Bottomley
2011-03-21 22:37 ` Brian King
2011-03-21 22:22 ` Brian King
2011-03-21 22:31 ` Brian King
2011-03-21 22:48 ` Nicholas A. Bellinger
2011-03-22 12:53 ` Brian King
2011-03-22 22:06 ` Nicholas A. Bellinger
2011-03-22 22:49 ` FUJITA Tomonori
2011-03-23 1:35 ` Nicholas A. Bellinger
2011-03-23 5:12 ` FUJITA Tomonori
2011-03-23 8:26 ` Nicholas A. Bellinger
2011-03-23 8:48 ` FUJITA Tomonori
2011-03-23 10:00 ` Nicholas A. Bellinger
2011-03-23 12:04 ` FUJITA Tomonori
2011-03-23 21:17 ` Nicholas A. Bellinger
2011-03-24 1:54 ` FUJITA Tomonori
2011-03-24 7:29 ` Nicholas A. Bellinger
2011-03-23 15:19 ` Brian King
2011-03-23 20:34 ` Nicholas A. Bellinger
2011-03-25 14:33 ` Brian King
2011-03-25 20:13 ` Nicholas A. Bellinger
2011-03-21 22:34 ` Nicholas A. Bellinger
2011-03-21 23:06 ` FUJITA Tomonori
2011-03-21 23:13 ` Nicholas A. Bellinger
2011-03-21 23:22 ` FUJITA Tomonori
2011-03-22 0:03 ` Nicholas A. Bellinger
2011-03-21 23:30 ` FUJITA Tomonori
2011-02-14 1:42 ` FUJITA Tomonori
2011-02-14 1:42 ` FUJITA Tomonori
2011-02-14 7:16 ` Bart Van Assche
2011-02-14 9:11 ` FUJITA Tomonori
2011-02-14 9:18 ` Nicholas A. Bellinger
2011-02-14 9:19 ` Nicholas A. Bellinger
2011-02-14 9:31 ` FUJITA Tomonori
2011-02-14 9:29 ` Nicholas A. Bellinger
2011-02-14 11:50 ` Bart Van Assche
2011-02-15 3:42 ` FUJITA Tomonori
2011-02-15 19:20 ` Bart Van Assche
2011-02-15 23:21 ` FUJITA Tomonori
2011-02-10 18:34 ` [PATCH 0/3] ibmvscsis driver rewrite Nicholas A. Bellinger
2011-02-14 1:36 ` FUJITA Tomonori
2011-02-14 8:48 ` Nicholas A. Bellinger
[not found] ` <4D53DE96.2020502@suse.de>
[not found] ` <1297363312.18212.153.camel@haakon2.linux-iscsi.org>
2011-02-10 21:22 ` Bart Van Assche [this message]
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=AANLkTikN4dRuAXg26LrPa65WpWfBG1CHwmctGOGwmFWE@mail.gmail.com \
--to=bvanassche@acm.org \
--cc=alex@csgraf.de \
--cc=benh@kernel.crashing.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanha@gmail.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).