linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Suleiman Souhlal <ssouhlal@freebsd.org>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Make the IDE DMA timeout modifiable
Date: Sat, 16 Jun 2007 01:23:55 +0200	[thread overview]
Message-ID: <200706160123.55636.bzolnier@gmail.com> (raw)
In-Reply-To: <466EEFD6.9030001@ru.mvista.com>

On Tuesday 12 June 2007, Sergei Shtylyov wrote:
> Bartlomiej Zolnierkiewicz wrote:
> >>On Feb 20, 2007, at 5:44 PM, Bartlomiej Zolnierkiewicz wrote:
> 
> >>>On Wednesday 21 February 2007 02:19, Suleiman Souhlal wrote:
> 
> >>>>It can be changed via /proc/ide/hd?/settings.
> 
> >>>Why do we need to change IDE DMA timeout dynamically?
> 
> >>I've used it to test error recovery (for example).
> 
> > Seems quite useable for developers but I would prefer not to
> > expose it in production kernels for end users.
> 
>     It seems that I have counter example of a customer asking if this timeout 
> can be done configurable. :-)

May I ask what was the rationale for this request?

I have no strong feelings about adding this /proc/ide/ setting but I worry
that it could be (mis)used just to (unreliably) work-around problems...

>     BTW, why the timeout is so damn long? 2*WAIT_CMD is 20 secs, and if DMA is 
> not complete or interrupt pending, it may wait 10 more secs...

I really don't remember... :)

Maybe Mark or Alan could help with figuring this out.

Thanks,
Bart

  reply	other threads:[~2007-06-15 23:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21  1:19 [PATCH 1/3] Make the IDE DMA timeout modifiable Suleiman Souhlal
2007-02-21  1:44 ` Bartlomiej Zolnierkiewicz
2007-02-21  2:13   ` Suleiman Souhlal
2007-02-21  2:42     ` Bartlomiej Zolnierkiewicz
2007-06-12 19:11       ` Sergei Shtylyov
2007-06-15 23:23         ` Bartlomiej Zolnierkiewicz [this message]
2007-07-10 19:10           ` Sergei Shtylyov
2007-07-13 15:16             ` Alan Cox
2007-07-13 15:12               ` Mark Lord
2007-07-13 15:21                 ` Sergei Shtylyov
2007-07-13 19:36                   ` Mark Lord
2007-07-13 19:40                     ` Sergei Shtylyov
2007-07-13 19:46                       ` Mark Lord
2007-07-13 20:03                         ` Sergei Shtylyov
2007-07-13 21:00                           ` Mark Lord
2007-07-16 19:29                             ` Rogier Wolff
2007-07-17 14:18                               ` Sergei Shtylyov
2007-07-13 20:08                     ` Sergei Shtylyov
2007-07-13 20:54                       ` Mark Lord
2007-07-13 21:00                         ` Mark Lord

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=200706160123.55636.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.com \
    --cc=ssouhlal@freebsd.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).