linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bokhan <aptem@ngs.ru>
To: Mark Lord <liml@rtr.ca>
Cc: Tejun Heo <htejun@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH #upstream-fixes] sata_mv: don't issue two DMA commands concurrently
Date: Thu, 14 Aug 2008 19:58:47 +0700	[thread overview]
Message-ID: <48A42C07.1050208@ngs.ru> (raw)
In-Reply-To: <48A427C0.1070500@rtr.ca>

That work, thanks, no retries at all now. But is behavior with readahead 
on and double reads correct?

Mark Lord пишет:
> Artem Bokhan wrote:
> ..
>> IMHO, looks like cavity somewhere... Any ideas?
> ..
>
> Have you tried to disable fs read-ahead?
>
> Something like "hdparm -a0 /dev/sd*" ?
>
> -ml


  reply	other threads:[~2008-08-14 12:58 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-08 10:02 bad sectors, suspicious behaviour Artem Bokhan
2008-08-08 13:34 ` Mark Lord
2008-08-08 13:50   ` Mark Lord
2008-08-08 14:14     ` Mark Lord
2008-08-11 11:12       ` Bokhan Artem
2008-08-13  8:40       ` Tejun Heo
2008-08-13 10:47         ` Artem Bokhan
2008-08-13 10:50           ` Tejun Heo
2008-08-13 11:19             ` Artem Bokhan
2008-08-13 11:24               ` [PATCH #upstream-fixes] sata_mv: don't issue two DMA commands concurrently Tejun Heo
2008-08-13 11:37                 ` Artem Bokhan
2008-08-13 11:52                   ` Tejun Heo
2008-08-13 12:05                     ` Artem Bokhan
2008-08-13 12:21                       ` Tejun Heo
2008-08-13 12:32                         ` Artem Bokhan
2008-08-13 16:17                       ` Mark Lord
2008-08-13 17:37                         ` Bokhan Artem
2008-08-13 19:58                         ` Bokhan Artem
2008-08-13 23:36                           ` Mark Lord
2008-08-14  7:42                             ` Artem Bokhan
2008-08-14 12:40                               ` Mark Lord
2008-08-14 12:58                                 ` Artem Bokhan [this message]
2008-08-14 13:17                                 ` Artem Bokhan
2008-08-14 19:49                                   ` Mark Lord
2008-08-15  5:35                                     ` Artem Bokhan
2008-08-15 12:27                                       ` Mark Lord
2008-08-13 16:57                       ` Greg Freemyer
2008-08-13 17:29                         ` Bokhan Artem
2008-08-13 17:50                           ` Greg Freemyer
2008-08-13 18:04                             ` Bokhan Artem
2008-08-13 18:13                               ` Greg Freemyer
2008-08-13 11:47                 ` Artem Bokhan
2008-08-13 11:52                   ` Tejun Heo
2008-08-22 16:28                     ` Grant Grundler
2008-08-13 16:10                 ` Mark Lord
2008-08-22  6:11                 ` Jeff Garzik
2008-08-22 17:01                   ` Martin Michlmayr
2008-08-26 13:54                     ` Mark Lord
2008-08-29  7:12                       ` Martin Michlmayr
2008-08-26  1:24                 ` Gwendal Grignou
2008-08-26  7:04                   ` Tejun Heo
2008-08-26 13:58                     ` 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=48A42C07.1050208@ngs.ru \
    --to=aptem@ngs.ru \
    --cc=htejun@gmail.com \
    --cc=liml@rtr.ca \
    --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).