From: Jens Axboe <jens.axboe@oracle.com>
To: Bart Van Assche <bart.vanassche@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Eric.Moore@lsi.com, jeff@garzik.org
Subject: Re: [PATCH 0/3]: blk-iopoll, a polled completion API for block devices
Date: Tue, 11 Aug 2009 19:14:27 +0200 [thread overview]
Message-ID: <20090811171427.GV12579@kernel.dk> (raw)
In-Reply-To: <e2e108260908110759w4fbbb5dejf852ba272fa29d75@mail.gmail.com>
On Tue, Aug 11 2009, Bart Van Assche wrote:
> On Tue, Aug 11, 2009 at 4:39 PM, Jens Axboe<jens.axboe@oracle.com> wrote:
> > On Tue, Aug 11 2009, Bart Van Assche wrote:
> >> On Thu, Aug 6, 2009 at 9:58 PM, Jens Axboe <jens.axboe@oracle.com> wrote:
> >> > Anyway, YMMV, I would appreciate some test results (and as usual, that
> >> > even includes just saying that it boots and functions for you). If
> >> > people feel adventurous, patches for other controllers will be happily
> >> > queued up for testing. I may even be convinced to implement support
> >> > for your controller of choice, if you have some fast storage hooked up
> >> > and would like to experiment. Generally, adding support to a driver is
> >> > not very hard and the two conversions included were also meant to serve
> >> > as an inspiration.
> >>
> >> Sounds very interesting. Have you already considered patching the SRP
> >> initiator ? During the SRP performance tests I ran CPU usage on the
> >> initiator was more than 95% and on the target less than 10%.
> >
> > No I haven't, if you point me at which srp files, I can take a look.
>
> The relevant source files are:
> include/scsi/srp.h
> include/scsi/scsi_transport_srp.h
> drivers/infiniband/ulp/srp/ib_srp.h
> drivers/infiniband/ulp/srp/ib_srp.c
> drivers/scsi/scsi_transport_srp.c
> drivers/scsi/libsrp.c
> drivers/scsi/scsi_transport_srp_internal.h
I can find | grep too :-)
Did you profile this? Where did it burn all the CPU time on the
initiator side?
--
Jens Axboe
next prev parent reply other threads:[~2009-08-11 17:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 19:58 [PATCH 0/3]: blk-iopoll, a polled completion API for block devices Jens Axboe
2009-08-06 19:58 ` [PATCH 1/3] block: add blk-iopoll, a NAPI like approach " Jens Axboe
2009-08-06 21:32 ` Alan Cox
2009-08-07 6:37 ` Jens Axboe
2009-08-07 8:38 ` Jeff Garzik
2009-08-07 8:50 ` Jens Axboe
2009-08-07 11:05 ` Jens Axboe
2009-08-07 11:31 ` Jens Axboe
2009-08-19 19:08 ` Jens Axboe
2009-08-20 11:30 ` [PATCH 1/3] block: add blk-iopoll, a NAPI like approach forblock devices jack wang
2009-08-20 11:38 ` Jens Axboe
2009-08-06 19:58 ` [PATCH 2/3] libata: add support for blk-iopoll Jens Axboe
2009-08-10 17:15 ` Jonathan Corbet
2009-08-10 17:22 ` Jens Axboe
2009-08-06 19:58 ` [PATCH 3/3] mptfusion: " Jens Axboe
2009-08-11 10:35 ` [PATCH 0/3]: blk-iopoll, a polled completion API for block devices Bart Van Assche
2009-08-11 14:39 ` Jens Axboe
2009-08-11 14:59 ` Bart Van Assche
2009-08-11 17:14 ` Jens Axboe [this message]
2009-08-11 18:37 ` Bart Van Assche
2009-08-11 18:41 ` Jens Axboe
2009-08-11 18:49 ` Bart Van Assche
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=20090811171427.GV12579@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Eric.Moore@lsi.com \
--cc=bart.vanassche@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 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).