From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 2/2] ata_piix: Enable parallel scan
Date: Wed, 10 Jun 2009 11:06:17 -0400 [thread overview]
Message-ID: <4A2FCBE9.9060505@garzik.org> (raw)
In-Reply-To: <20090513140233.11247.66014.stgit@t61.ukuu.org.uk>
Alan Cox wrote:
> From: Arjan van de Ven <arjan@infradead.org>
>
> This patch turns on parallel scanning for the ata_piix driver.
> This driver is used on most netbooks (no AHCI for cheap storage it seems).
> The scan is the dominating time factor in the kernel boot for these
> devices; with this flag it gets cut in half for the device I used
> for testing (eeepc).
> Alan took a look at the driver source and concluded that it ought to be safe
> to do for this driver. Alan has also checked with the hardware team.
>
> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> ---
>
> drivers/ata/ata_piix.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
>
> diff --git a/drivers/ata/ata_piix.c b/drivers/ata/ata_piix.c
> index 0fba112..4ea02a7 100644
> --- a/drivers/ata/ata_piix.c
> +++ b/drivers/ata/ata_piix.c
> @@ -1580,6 +1580,7 @@ static int __devinit piix_init_one(struct pci_dev *pdev,
> host->ports[1]->mwdma_mask = 0;
> host->ports[1]->udma_mask = 0;
> }
> + host->flags |= ATA_HOST_PARALLEL_SCAN;
>
> pci_set_master(pdev);
> return ata_pci_sff_activate_host(host, ata_sff_interrupt, &piix_sht);
applied... let's see what explodes
prev parent reply other threads:[~2009-06-10 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 14:01 [PATCH 0/2] Series short description Alan Cox
2009-05-13 14:02 ` [PATCH 1/2] libata: Use IGN_SIMPLEX for ALi Alan Cox
2009-05-13 15:56 ` Sergei Shtylyov
2009-05-13 16:11 ` Alan Cox
2009-05-20 20:11 ` Jeff Garzik
2009-05-13 14:02 ` [PATCH 2/2] ata_piix: Enable parallel scan Alan Cox
2009-06-10 15:06 ` Jeff Garzik [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=4A2FCBE9.9060505@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@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).