From: Rob Evers <revers@redhat.com>
To: Rob Evers <revers@redhat.com>
Cc: linux-scsi@vger.kernel.org, michaelc@cs.wisc.edu,
bvanassche@acm.org, emilne@redhat.com
Subject: Re: [PATCH V3 0/4] Configure number of LUs reported by 'report-luns'
Date: Thu, 07 Mar 2013 12:01:24 -0500 [thread overview]
Message-ID: <5138C7E4.9010503@redhat.com> (raw)
In-Reply-To: <1362663515-3476-1-git-send-email-revers@redhat.com>
On 03/07/2013 08:38 AM, Rob Evers wrote:
> This patch set retrieves the number of LUs available on a target
> using the report-luns command. The initial size of the report-luns
> command is 512 entries, as the previous default initial number was.
> If more LUs than 511 are present on a target, the report-luns is
> re-issued with the size indicated in the result of the original
> report-luns, up to max_report_luns.
>
> The default value of max_report_luns is increased to 16k-1 from 512-1.
>
> 3rd version changes from 2nd posting:
>
> - add a patch to use get/put_unaligned_be32() in report-luns code
>
> 2nd version changes from first posting:
>
> - Minor tweak added in 2nd patch to use the number of luns
> reported in the 2nd report-luns command, if it is executed.
> There is a chance that the number changed between the
> 1st and 2nd report-luns.
>
> - Add 3rd patch changing kmalloc flag in report luns from
> GFP_ATOMIC to GFP_KERNEL, as this is more consistent with
> the allocation flag in blk_alloc_queue_node()
>
> Rob Evers (4):
> Encapsulate scsi_do_report_luns
> Configure reported luns
> Change kmallocs in report_luns to use GFP_KERNEL
> Use set/get_unaligned_be32 in report_luns
>
> drivers/scsi/scsi_scan.c | 192 +++++++++++++++++++++++++++++------------------
> 1 file changed, 120 insertions(+), 72 deletions(-)
>
All patches in series Signed-off-by: Rob Evers <revers@redhat.com>
prev parent reply other threads:[~2013-03-07 17:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 13:38 [PATCH V3 0/4] Configure number of LUs reported by 'report-luns' Rob Evers
2013-03-07 13:38 ` [PATCH V3 1/4] Encapsulate scsi_do_report_luns Rob Evers
2013-03-07 15:47 ` Elliott, Robert (Server Storage)
2013-03-07 16:06 ` Jeremy Linton
2013-03-07 17:01 ` Elliott, Robert (Server Storage)
2013-03-07 17:30 ` James Bottomley
2013-03-07 17:38 ` Elliott, Robert (Server Storage)
2013-03-07 17:48 ` James Bottomley
2013-03-07 17:42 ` Jeremy Linton
2013-03-07 13:38 ` [PATCH V3 2/4] Configure reported luns Rob Evers
2013-03-07 13:38 ` [PATCH V3 3/4] Change kmallocs in report_luns to use GFP_KERNEL Rob Evers
2013-03-07 13:38 ` [PATCH V3 4/4] Use set/get_unaligned_be32 in report_luns Rob Evers
2013-03-07 14:31 ` [PATCH V3 0/4] Configure number of LUs reported by 'report-luns' Ewan Milne
2013-03-07 17:01 ` Rob Evers [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=5138C7E4.9010503@redhat.com \
--to=revers@redhat.com \
--cc=bvanassche@acm.org \
--cc=emilne@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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