From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: James Bottomley <James.Bottomley@suse.de>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: make scsi_devinfo infrastructure optional
Date: Sat, 12 Feb 2011 21:54:43 +0100 [thread overview]
Message-ID: <20110212205443.GA2912@joi.lan> (raw)
In-Reply-To: <201102121316.51333.bzolnier@gmail.com>
On Sat, Feb 12, 2011 at 01:16:50PM +0100, Bartlomiej Zolnierkiewicz wrote:
> From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> Subject: [PATCH] scsi: make scsi_devinfo table content optional
>
> Add CONFIG_SCSI_QUIRKS config option (default y and dependent
> on EMBEDDED config option) to allow disabling of the default
> scsi_devinfo table content.
Note: all uses of CONFIG_EMBEDDED were recently moved to CONFIG_EXPERT.
(see commit 6a108a14fa356ef607be308b68337939e56ea94e)
This one should probably use it too.
>
> The output code size savings are ~7.5k for CONFIG_SCSI_QUIRKS=n
> (as measured on x86-64):
>
> CONFIG_SCSI_QUIRKS=y:
> text data bss dec hex filename
> 5965 5520 288 11773 2dfd drivers/scsi/scsi_devinfo.o
>
> CONFIG_SCSI_QUIRKS=n:
> text data bss dec hex filename
> 3740 48 288 4076 fec drivers/scsi/scsi_devinfo.o
>
> Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
> ---
> drivers/scsi/Kconfig | 9 +++++++++
> drivers/scsi/scsi_devinfo.c | 2 ++
> 2 files changed, 11 insertions(+)
>
> Index: b/drivers/scsi/Kconfig
> ===================================================================
> --- a/drivers/scsi/Kconfig
> +++ b/drivers/scsi/Kconfig
> @@ -47,6 +47,15 @@ config SCSI_TGT
> If you want to use SCSI target mode drivers enable this option.
> If you choose M, the module will be called scsi_tgt.
>
> +config SCSI_QUIRKS
> + bool "SCSI quirks list" if EMBEDDED
> + default y
> + help
> + This option enables deprecated in-kernel list of devices
> + that require settings that differ from the default.
> +
> + If unsure say Y.
> +
> config SCSI_NETLINK
> bool
> default n
> Index: b/drivers/scsi/scsi_devinfo.c
> ===================================================================
> --- a/drivers/scsi/scsi_devinfo.c
> +++ b/drivers/scsi/scsi_devinfo.c
> @@ -53,6 +53,7 @@ static struct {
> char *revision; /* revision known to be bad, unused */
> unsigned flags;
> } scsi_static_device_list[] __initdata = {
> +#ifdef CONFIG_SCSI_QUIRKS
> /*
> * The following devices are known not to tolerate a lun != 0 scan
> * for one reason or another. Some will respond to all luns,
> @@ -251,6 +252,7 @@ static struct {
> {"XYRATEX", "RS", "*", BLIST_SPARSELUN | BLIST_LARGELUN},
> {"Zzyzx", "RocketStor 500S", NULL, BLIST_SPARSELUN},
> {"Zzyzx", "RocketStor 2000", NULL, BLIST_SPARSELUN},
> +#endif
> { NULL, NULL, NULL, 0 },
> };
>
> --
prev parent reply other threads:[~2011-02-12 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 14:15 [PATCH] scsi: make scsi_devinfo infrastructure optional Bartlomiej Zolnierkiewicz
2011-02-09 18:00 ` James Bottomley
2011-02-10 9:18 ` Bartlomiej Zolnierkiewicz
2011-02-10 15:07 ` James Bottomley
2011-02-11 9:52 ` Bartlomiej Zolnierkiewicz
2011-02-11 16:06 ` James Bottomley
2011-02-12 12:16 ` Bartlomiej Zolnierkiewicz
2011-02-12 20:54 ` Marcin Slusarz [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=20110212205443.GA2912@joi.lan \
--to=marcin.slusarz@gmail.com \
--cc=James.Bottomley@suse.de \
--cc=bzolnier@gmail.com \
--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).