9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: Re: [9fans] Any one going to change to sata disks?
Date: Thu, 29 Jun 2006 14:54:28 -0700	[thread overview]
Message-ID: <5139923321f1b64b0bef6e817925e70c@collyer.net> (raw)
In-Reply-To: <14ec7b180606291403n66dbbc02y242600363e47c5dc@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 129 bytes --]

Andrey, are you using a Marvell controller, or one that looks to
software like an IDE/(P)ATA controller (e.g., Silicon Image)?

[-- Attachment #2: Type: message/rfc822, Size: 3884 bytes --]

From: "andrey mirtchovski" <mirtchovski@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: [9fans] Any one going to change to sata disks?
Date: Thu, 29 Jun 2006 15:03:36 -0600
Message-ID: <14ec7b180606291403n66dbbc02y242600363e47c5dc@mail.gmail.com>

here's my recent experience with sata:

i had two disks i wanted to use, big 250gb chunks of hunk. if one was
plugged in by itself it will appear as sdC0, if i plugged in a second
one none of the two will be recognized, not even to boot from. one had
to keep switching them from one slot to the other and fiddling with
the bios just to get them both to be visible to the os. if anything
was plugged in to the IDE slots, including just a cdrom, the sata
disks (or one disk, rather) would be delegated to sdE0...

with two sata disks plugged in as sdC0 and sdD0, the bandwidth to one
would be 5 times slower than the bandwidth to the other. same test as
jmk's would complete in 2-3 seconds on sdC0, and 11-12 seconds on
sdD0...

  parent reply	other threads:[~2006-06-29 21:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 19:13 Francisco J Ballesteros
2006-06-29 19:18 ` Brantley Coile
2006-06-29 19:54   ` jmk
2006-06-29 21:03     ` andrey mirtchovski
2006-06-29 21:35       ` jmk
2006-06-29 21:49         ` Ronald G Minnich
2006-06-29 21:54       ` geoff [this message]
2006-06-29 22:00         ` Re: " andrey mirtchovski
2006-06-29 22:01       ` Francisco J Ballesteros
2006-06-29 22:57         ` Ronald G Minnich
2006-06-30 14:00           ` Brantley Coile
2006-06-30 14:10             ` quanstro
2006-06-30 14:28               ` Brantley Coile
2006-06-30 15:00                 ` quanstro
2006-06-30 15:36                   ` Brantley Coile
2006-06-30  0:17         ` Jack Johnson
2006-06-30  0:48           ` jmk
2006-06-30  0:52           ` geoff
2006-06-30 16:09             ` Jack Johnson
2006-06-30 16:53               ` Jack Johnson
2006-06-30 18:28               ` jmk
2006-06-30 18:32                 ` Ronald G Minnich
2006-06-30 18:36                 ` Re: " andrey mirtchovski
2006-06-30 19:13                   ` jmk
2006-06-30 20:16                   ` David Leimbach
2006-06-30 19:04                 ` Jack Johnson
2006-06-30 22:33                   ` geoff
2006-07-01  4:17                     ` geoff
2006-06-29 22:06   ` geoff

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=5139923321f1b64b0bef6e817925e70c@collyer.net \
    --to=geoff@collyer.net \
    --cc=9fans@cse.psu.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 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).