From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Patrick Ale" <patrick.ale@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libsata tests started
Date: Sat, 10 Feb 2007 11:41:55 -0800 [thread overview]
Message-ID: <20070210114155.6f7433c8.randy.dunlap@oracle.com> (raw)
In-Reply-To: <8d158e1f0702100822i28d0bcds91cf27fc34534d2c@mail.gmail.com>
On Sat, 10 Feb 2007 17:22:28 +0100 Patrick Ale wrote:
> Hi,
>
> And now for something completely different.
>
> I started the libsata tests on one of the four machines I'll be doing
> these tests on.
Hi,
What are the libsata tests and where are they, please?
> At the moment I'm testing on 'lilith', which is my multi-harddisk
> server and playground.
>
> At the moment I am hammering /dev/sda5, which is an ext4dev partition
> with bonnie++.
> sda is attached to my onboard ATA controller, driven by pata_via.
So you are testing libata and ext4dev at the same time...
> At the same moment I am doing a full resync of my MD RAID1 device with
> two stripes.
> Both stripes are on seperate 120GB disks, where one disk is attached
> to a PCI controller, driven by pata_sil680 and one disk attached to an
> onboard Promise ATA controller, driven by pata_pdc2027x.
>
> I confirmed that all devices are driven by the new libsata drivers, it
> can't be very much differentr since I disabled the entire "old" IDE
> stack. :)
libsata == libata ?
> So, let's see how things go, so far so good.
>
> For those who are interested, I attached the output of an lspci -vvv.
> The file name has "stage1" included since I'll be adding my PCI cards
> one by one to isolate problems to a single bus or card.
>
> I hope my test input helps a bit.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-02-10 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-10 16:22 libsata tests started Patrick Ale
2007-02-10 19:41 ` Randy Dunlap [this message]
2007-02-10 20:14 ` Patrick Ale
2007-02-10 20:35 ` Alan
2007-02-10 20:32 ` Patrick Ale
2007-02-10 22:04 ` Patrick Ale
2007-02-10 22:23 ` Michal Piotrowski
2007-02-13 8:31 ` Patrick Ale
2007-02-15 4:57 ` Tejun Heo
2007-02-15 16:16 ` Patrick Ale
2007-02-15 16:18 ` Patrick Ale
2007-02-15 19:37 ` Ioan Ionita
2007-02-15 20:07 ` Patrick Ale
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=20070210114155.6f7433c8.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patrick.ale@gmail.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