All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Jayamohan Kalickal <jayamohank@serverengines.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/6] RFC: beiscsi : handles core routines
Date: Mon, 03 Aug 2009 17:18:31 -0500	[thread overview]
Message-ID: <4A776237.6020302@cs.wisc.edu> (raw)
In-Reply-To: <20090803204131.GV12579@kernel.dk>

Jens Axboe wrote:
> On Mon, Aug 03 2009, Mike Christie wrote:
>> Hey Jens,
>>
>> Is your block napi code going to go upstream soon? Does it need more  
>> testing or users?
>>
>> This driver is just using a normal old work queue for the completion  
>> path, so I wanted to see about having Jay convert it to your code.
> 
> I plan to include the core bits for 2.6.32, so should be heading to
> mainline soon(ish) :-)
> 

Thanks.

Jay, please look at Jens's block tree
http://git.kernel.org/?p=linux/kernel/git/axboe/linux-2.6-block.git;a=summary
In that tree there is a blk-iopoll branch that you will want to use to 
convert your completion handling to.

  reply	other threads:[~2009-08-03 22:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28  7:13 [PATCH 1/6] RFC: beiscsi : handles core routines Jayamohan Kallickal
2009-07-28 13:13 ` Rolf Eike Beer
2009-07-28 20:12 ` Rolf Eike Beer
2009-08-03 16:57 ` Mike Christie
2009-08-03 20:41   ` Jens Axboe
2009-08-03 22:18     ` Mike Christie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-13  7:08 Jayamohan Kallickal
2009-08-13 10:09 ` Rolf Eike Beer
2009-08-20 19:26 ` Mike Christie
2009-07-27 19:55 RFC: be iscsi driver Jayamohan Kallickal
     [not found] ` <1248724523-10999-1-git-send-email-jayamohank-i5Eg4PDOvn3+uv41P6q33AC/G2K4zDHf@public.gmane.org>
2009-07-27 19:55   ` [PATCH 1/6] RFC: beiscsi : handles core routines Jayamohan Kallickal

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=4A776237.6020302@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=jayamohank@serverengines.com \
    --cc=jens.axboe@oracle.com \
    --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 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.