All of lore.kernel.org
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <kernel@nn7.de>
To: Tejun Heo <htejun@gmail.com>
Cc: Matteo Croce <rootkit85@yahoo.it>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] AHCI PCI ID for MacBook Pro
Date: Sat, 10 Feb 2007 17:03:37 +0100	[thread overview]
Message-ID: <1171123417.31813.4.camel@localhost> (raw)
In-Reply-To: <45CDC5DF.9060306@gmail.com>

On Sat, 2007-02-10 at 08:17 -0500, Tejun Heo wrote:
> Soeren Sonnenburg wrote:
> > On Fri, 2007-02-09 at 18:41 +0100, Matteo Croce wrote:
> >> On Friday 09 February 2007 16:45:49 you wrote:
> >>> On Fri, 2007-02-09 at 04:33 -0500, Tejun Heo wrote:
> >>>> Root Kit wrote:
> >>> [...]
> >>> Hmmhh I cannot really reproduce this benchmark. Matteo, with which
> >>> benchmarking program did you produce this ?
> >>> [...]
> >> bonnie++ from ubuntu repos
> > 
> > OK, I reran bonnie++ -d /tmp/ on a unencrypted partition - results are
> > here http://nn7.de/bench/ahci.html . Looks like it is slightly faster
> > for sequential block write (2MB/s faster) and sequential read using
> > putc()  (1MB/s faster), though putc() is slowed down by 6MB/s.
> 
> I suspect the difference is caused by either the io scheduler in use or 
> disk drive itself.

well I am doing both benchmarks on a macbookpro1,1 -> 32bit mode (matteo
does it on a macbook pro2, sth so he has a c2d and does it in 64bit ->
amd64 mode).

So the io scheduler is the same or do you mean inside of ahci/piix ?

> > However what may make it worth is that I don't see any errors on
> > suspend/resume anymore...
> 
> Hmm... So, ata_piix fails to suspend/resume properly on your machine? 
> It should work.  Can you describe how it fails?

Well I keep seeing this:

ata3.01: revalidation failed (errno=-2)
ata3: failed to recover some devices, retrying in 5 secs
ATA: abnormal status 0x7F on port 0x40DF
ATA: abnormal status 0x7F on port 0x40DF
ata3.01: configured for UDMA/133

but I am still on 2.6.20-rc6 ... so sorry if this is now fixed in .20.

Soeren.
-- 
Sometimes, there's a moment as you're waking, when you become aware of
the real world around you, but you're still dreaming.

  reply	other threads:[~2007-02-10 16:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08 17:33 [PATCH] AHCI PCI ID for MacBook Pro Root Kit
2007-02-09  9:33 ` Tejun Heo
2007-02-09 14:27   ` Matteo Croce
2007-02-09 14:54     ` David M. Lloyd
2007-02-09 17:39       ` Matteo Croce
2007-02-09 18:15         ` David M. Lloyd
2007-02-09 18:51           ` Matteo Croce
2007-02-10 10:22           ` Soeren Sonnenburg
2007-02-10 14:03         ` Tejun Heo
2007-02-10 16:07           ` Soeren Sonnenburg
2007-02-10 17:10             ` Tejun Heo
2007-02-11 15:40           ` David M. Lloyd
2007-02-09 15:45   ` Soeren Sonnenburg
2007-02-09 17:41     ` Matteo Croce
2007-02-10 10:19       ` Soeren Sonnenburg
2007-02-10 13:17         ` Tejun Heo
2007-02-10 16:03           ` Soeren Sonnenburg [this message]
2007-02-10 17:17             ` Tejun Heo

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=1171123417.31813.4.camel@localhost \
    --to=kernel@nn7.de \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=rootkit85@yahoo.it \
    /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.