All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Frederik Deweerdt <frederik.deweerdt@xprog.eu>,
	linux-ide@vger.kernel.org,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Limiting DMA speeds for individual IDE drives
Date: Tue, 08 Sep 2009 22:04:22 +0400	[thread overview]
Message-ID: <4AA69CA6.9050909@ru.mvista.com> (raw)
In-Reply-To: <20090908161204.GA3113@gambetta>

Hello.

Frederik Deweerdt wrote:

>>Is there any simple way to force the old IDE driver to limit the DMA
>>speed for a particular device?

    No, you can only disable DMA totally, and then set the needed speed via 
hdparm.

>>I've got a situation where a drive claims to be capable of supporting
>>UDMA/100, but it's in a noisy environment and gets lots of errors at
>>that speed.  I'd like to limit it to UDMA/66 or even UDMA/33.

    Are you sure that it's all because of the noise and not a cable type 
misdetection?

>>The hdparm command should be able to do this but I can't run it until 
>>the system has booted, by which time a bunch of CRC and possibly other 
>>errors have already occurred.  Ideally it should be possible to limit 
>>the speed starting as early as device detection, but I can't find any 
>>way to do it.  Is there support for such a thing or will I have to hack 
>>it in?

> Does passing ide=nodma at bootime, and then having init set the DMA at
> the right speed, would work?

    ide=nodma is now obsolete -- use ide_core.nodma=<interface>,<device> 
instead. Read Documentation/ide/ide.txt before advising. ;-)

> Regards,
> Frederik

WBR, Sergei

  reply	other threads:[~2009-09-08 18:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 16:03 Limiting DMA speeds for individual IDE drives Alan Stern
2009-09-08 16:24 ` Frederik Deweerdt
2009-09-08 18:04   ` Sergei Shtylyov [this message]
2009-09-08 17:53 ` Alan Cox
2009-09-08 18:18   ` Alan Stern
2009-09-09  6:46     ` Thomas Fjellstrom

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=4AA69CA6.9050909@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=frederik.deweerdt@xprog.eu \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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.