linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Matti Linnanvuori <mattilinnanvuori@yahoo.com>
Cc: bzolnier@gmail.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH] drivers/ide/Kconfig IDEPCI_SHARE_IRQ and IDEDISK_MULTI_MODE
Date: Mon, 22 Oct 2007 17:23:44 +0400	[thread overview]
Message-ID: <471CA460.5040107@ru.mvista.com> (raw)
In-Reply-To: <604640.68715.qm@web52004.mail.re2.yahoo.com>

Matti Linnanvuori wrote:

> Correct IDEPCI_SHARE_IRQ description to keeping interrupts enabled
> when calling the PCI IDE action handler.
> Add IDEPCI_SHARE_IRQ and IDEDISK_MULTI_MODE help text from hdparm
> manual page.

> Signed-off-by: Matti Linnanvuori <mattilinnanvuori@yahoo.com>

    NAK.

> @@ -154,6 +154,18 @@ config BLK_DEV_IDEDISK
>  config IDEDISK_MULTI_MODE
>  	bool "Use multi-mode by default"
>  	help
> +	  Multiple sector mode is a feature of most modern IDE hard
> + 	  drives, permitting the transfer of multiple sectors per I/O
> +	  interrupt, rather than the usual one sector per interrupt.
> +	  When this feature is enabled, it typically reduces operating
> +	  system overhead for disk I/O by 30-50%. On many systems, it
> +	  also provides increased data throughput of anywhere from 5%
> +	  to 50%. Some drives, however (most notably the WD Caviar
> +	  series), seem to run slower with multiple mode enabled. Some
> +	  drives claim to support multiple mode, but lose data at some
> +	  settings. Under rare circumstances, such failures can result

    The speed increase data provided here are largely useless, since multiple 
mode only applies to PIO transfers. At least, the comment should make this 
clear...

> +	  in massive filesystem corruption.
> +
>  	  If you get this error, try to say Y here:
>  
>  	  hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> @@ -367,11 +379,16 @@ config BLK_DEV_IDEPCI
>  	bool
>  
>  config IDEPCI_SHARE_IRQ
> -	bool "Sharing PCI IDE interrupts support"
> +	bool "Keeping interrupts enabled when calling the PCI IDE action handler support"

    Keeping IRQ enabled is only a side effect of IRQ sharing...

>  	depends on BLK_DEV_IDEPCI
>  	help
> -	  Some ATA/IDE chipsets have hardware support which allows for
> -	  sharing a single IRQ with other cards. To enable support for
> +	  A setting of Y permits the driver to unmask other interrupts
> +	  during processing of a disk interrupt, which greatly improves
> + 	  Linux's responsiveness and eliminates "serial port overrun"
> +	  errors. Use this feature with caution: some drive/controller
> +	  combinations do not tolerate the increased I/O latencies
> +	  possible when this feature is enabled, resulting in massive
> +	  filesystem corruption. To enable support for
>  	  this in the ATA/IDE driver, say Y here.

    Comments do not really describe the IRQ sharing option anymore.

>  	  It is safe to say Y to this question, in most cases.

MBR, Sergei

      reply	other threads:[~2007-10-22 13:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-21  6:46 [PATCH] drivers/ide/Kconfig IDEPCI_SHARE_IRQ and IDEDISK_MULTI_MODE Matti Linnanvuori
2007-10-22 13:23 ` Sergei Shtylyov [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=471CA460.5040107@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mattilinnanvuori@yahoo.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 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).