From: Rob Evers <revers@redhat.com>
To: linux-scsi@vger.kernel.org
Subject: Re: [PATCH V5 0/3] scsi: Configure number of LUs reported by 'report-luns'
Date: Mon, 08 Dec 2014 08:04:13 -0500 [thread overview]
Message-ID: <5485A1CD.80804@redhat.com> (raw)
In-Reply-To: <1417808263-5632-1-git-send-email-revers@redhat.com>
On 12/05/2014 02:37 PM, Rob Evers wrote:
> This patch set retrieves the number of LUs available on a target
> using the report-luns command by re-sizing the returned data
> buffer and retrying report luns.
>
> A minor bug fix is included.
>
> scsi_mod parameter max_report_luns is no longer used and is removed.
>
> Changes from previous posting:
>
> - simplify implementation by removing max_report_luns parameter and
> removing 2nd kmalloc failure handling
>
> - remove patch to fix return value on first kmalloc failing
>
> - drop do_scsi_report_luns encapsulation as it isn't required
> with new implementation
>
> Rob Evers (3):
> scsi: Avoid unnecessary GFP_ATOMIC allocation in scsi_report_lun_scan
> scsi: Use set/get_unaligned_be32 in report_luns
> scsi: Retry report-luns when reported LU count requres more memory
>
> drivers/scsi/scsi_scan.c | 54 ++++++++++++++----------------------------------
> 1 file changed, 15 insertions(+), 39 deletions(-)
>
Patch set Signed-off-by: Rob Evers <revers@redhat.com>
prev parent reply other threads:[~2014-12-08 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 19:37 [PATCH V5 0/3] scsi: Configure number of LUs reported by 'report-luns' Rob Evers
2014-12-05 19:37 ` [PATCH V5 1/3] scsi: Avoid unnecessary GFP_ATOMIC allocation in scsi_report_lun_scan Rob Evers
2014-12-15 15:43 ` Christoph Hellwig
2014-12-05 19:37 ` [PATCH V5 2/3] scsi: Use set/get_unaligned_be32 in report_luns Rob Evers
2014-12-15 15:45 ` Christoph Hellwig
2014-12-05 19:37 ` [PATCH V5 3/3] scsi: Retry report-luns when reported LU count requres more memory Rob Evers
2014-12-15 15:47 ` Christoph Hellwig
2014-12-08 13:04 ` 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=5485A1CD.80804@redhat.com \
--to=revers@redhat.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.