From: Mike Christie <michaelc@cs.wisc.edu>
To: Vasu Dev <vasu.dev@linux.intel.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [RFC PATCH 0/9] RFC: handle queue_depth adjustments because of QUEUE_FULLs in scsi_error.c
Date: Tue, 01 Sep 2009 20:46:05 -0500 [thread overview]
Message-ID: <4A9DCE5D.2040208@cs.wisc.edu> (raw)
In-Reply-To: <1251845853.27437.69.camel@vi2.jf.intel.com>
On 09/01/2009 05:57 PM, Vasu Dev wrote:
> On Wed, 2009-08-26 at 11:03 -0700, Vasu Dev wrote:
>> First four patches are from Mike Christie's original RFC at:-
>>
>> http://www.spinics.net/lists/linux-scsi/msg35959.html
>> http://www.spinics.net/lists/linux-scsi/msg35962.html
>> http://www.spinics.net/lists/linux-scsi/msg35961.html
>> http://www.spinics.net/lists/linux-scsi/msg35963.html
>> http://www.spinics.net/lists/linux-scsi/msg35964.html
>>
>> Above four patches adds ramp down code and I appended ramp
>> up code in following patches and tested this entire
>> series with libfc/fcoe. This series works fine without any
>> regression and also queue_depth adjustment works for both
>> ramp down and ramp up.
>>
>> Above patches are updated to scsi-misc -rc7 plus recently
>> submitted 64 fcoe patches series by Rob
>> "[PATCH 00/64] libfc, libfcoe and fcoe updates for scsi-misc"
>> This series also applies cleanly to scsi-misc -rc7.
>>
>> I'd appreciate review comments for added more patches for
>> ramp up.
>>
>> I'll post my final patches to this list skipping fcoe list,
>> this as per Rob Love suggestion since mostly scsi changes
>> by this series beyond fcoe/libfc. However Rob agreed to
>> review/Ack fcoe/libfc changes at this list.
>>
>> Mike, I'll be able to post my ramp up patches only once
>> you send final patches for ramp down on which my patches
>> depends. As I said your patches are tested for libfc,
>> so most common code is already tested and they are
>> good go as far as libfc goes.
>>
>
> Hey Mike,
>
> I'd like to get final patches of this series out this week to
> get them into next merge window but not sure how to get final patches
> out with your first four RFC patches in this series on which rest all
> patches depends. Please help me on this.
>
You should just post your patches with mine. I do not have time to test
my stuff right now with the current kernel, and since you need them and
are going to have to test your patches just make it easy for
James/reviewers and send it all in one patchset so people do not have to
search for dependencies.
For my patches just add your signed off after mine, since you are
sending them and I had written them.
You can/should probably also pick up Christop's stuff too for him (zfcp
patches).
next prev parent reply other threads:[~2009-09-02 1:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 18:03 [RFC PATCH 0/9] RFC: handle queue_depth adjustments because of QUEUE_FULLs in scsi_error.c Vasu Dev
2009-08-26 18:03 ` [RFC PATCH 1/9] scsi-ml: modify change_queue_depth to take in reason why it is being called Vasu Dev
2009-08-27 10:21 ` Christof Schmitt
2009-08-27 21:09 ` Vasu Dev
2009-08-28 16:56 ` Mike Christie
2009-08-26 18:03 ` [RFC PATCH 2/9] scsi error: have scsi-ml call change_queue_depth to handle QUEUE_FULL Vasu Dev
2009-08-26 18:03 ` [RFC PATCH 3/9] drivers: convert drivers setting the change_queue_depth callback Vasu Dev
2009-08-26 18:19 ` Jeff Garzik
2009-08-26 21:50 ` Vasu Dev
2009-08-26 21:55 ` Mike Christie
2009-08-26 18:03 ` [RFC PATCH 4/9] drivers: convert fc drivers calling scsi_track_queue_full Vasu Dev
2009-08-26 18:03 ` [RFC PATCH 5/9] scsi: updates sdev to add queue_depth ramp up code Vasu Dev
2009-08-26 18:03 ` [RFC PATCH 6/9] scsi: adds sdev->queue_ramp_up_period to sysfs Vasu Dev
2009-08-26 18:03 ` [RFC PATCH 7/9] scsi: add common queue_depth ramp up code Vasu Dev
2009-08-26 18:03 ` [RFC PATCH 8/9] fcoe, libfc: fix an libfc issue with queue ramp down in libfc Vasu Dev
2009-08-26 18:04 ` [RFC PATCH 9/9] libfc: adds queue_depth ramp up to libfc Vasu Dev
2009-08-27 10:19 ` Christof Schmitt
2009-08-27 20:56 ` Vasu Dev
2009-08-28 10:44 ` Christof Schmitt
2009-09-02 18:00 ` Vasu Dev
2009-09-01 22:57 ` [RFC PATCH 0/9] RFC: handle queue_depth adjustments because of QUEUE_FULLs in scsi_error.c Vasu Dev
2009-09-02 1:46 ` Mike Christie [this message]
2009-09-02 18:01 ` Vasu Dev
2009-09-03 8:17 ` Swen Schillig
2009-09-14 11:21 ` Christof Schmitt
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=4A9DCE5D.2040208@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=linux-scsi@vger.kernel.org \
--cc=vasu.dev@linux.intel.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 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.