Linux Newbie help
 help / color / mirror / Atom feed
From: Aleksey Gorelov <dared1st@yahoo.com>
To: jengelh@linux01.gwdg.de, daniel.rodrick@gmail.com
Cc: linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org,
	linux-newbie@vget.kernel.org, satinder.jeet@gmail.com
Subject: RE: Generic Disk Driver in Linux
Date: Thu, 24 Aug 2006 11:19:35 -0700 (PDT)	[thread overview]
Message-ID: <20060824181935.90856.qmail@web83102.mail.mud.yahoo.com> (raw)

>From: linux-kernel-owner@vger.kernel.org 
>[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Jan Engelhardt
>>
>> I was curious that can we develop a generic disk driver that could
>> handle all the kinds of hard drives - IDE, SCSI, RAID et al?
>
>ide_generic
>sd_mod
>
>All there, what more do you want?

Unfortunately, not _all_. DMRAID does not support all fake raids yet. Moreover, there is usually
some gap for bleeding edge hw support.

>
>> I thought we could use the BIOS interrupt 13H for this purpose,
>>
>I fail to see a BIOS on non-x86 computers.
>
>> but ran into a LOT of real mode / protected mode issues.
>>
>Sure. We are not real mode.
>Ever heard of BIOS limitations? If no, first check out 
>http://www.pcguide.com/ref/hdd/bios/sizeGB8-c.html
  This is not really relevant. They actually answer it right in the article - BIOS extensions, aka
EDD.

  I'd say the performance issue is more in int13 non-dma vs. dma data transfers, and tricks
associated with vm86. Although most 'on board' BIOSes support dma just fine for single drives,
faik raid and 'plug-in' card option ROMS usually lacks any dma support. Plus, there is no way to
tell whether BIOS will do dma or pio upfront.
  Another problem here is that BIOSes usually support legacy PIC interrupt model, and modern OSes
use IO APIC and resteer the interrups.

Aleks.

>
>
>
>Jan Engelhardt
>-- 
>-
>To unsubscribe from this list: send the line "unsubscribe 
>linux-kernel" in

             reply	other threads:[~2006-08-24 18:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24 18:19 Aleksey Gorelov [this message]
2006-08-24 18:36 ` Generic Disk Driver in Linux Arjan van de Ven
2006-08-24 19:40   ` Aleksey Gorelov
2006-08-24 20:03     ` Arjan van de Ven
2006-08-24 22:21       ` Aleksey Gorelov
2006-08-25  8:03         ` Arjan van de Ven
2006-08-25 16:50           ` Aleksey Gorelov
2006-08-24 20:36     ` Phillip Susi
2006-08-24 22:27       ` Aleksey Gorelov
2006-08-25 10:21 ` Helge Hafting
2006-08-25 17:05   ` Aleksey Gorelov
2006-08-25 18:19     ` Greg Freemyer
2006-08-28 10:46     ` Helge Hafting
     [not found] <fa.RkJMFmeAVY9kZAODCPJ1Yc8Vtww@ifi.uio.no>
2006-08-25  0:12 ` Robert Hancock
  -- strict thread matches above, loose matches on Subject: below --
2006-08-24 12:47 Daniel Rodrick
2006-08-24 13:10 ` Jan Engelhardt
2006-08-24 16:54 ` Ralf Baechle

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=20060824181935.90856.qmail@web83102.mail.mud.yahoo.com \
    --to=dared1st@yahoo.com \
    --cc=daniel.rodrick@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-newbie@vget.kernel.org \
    --cc=satinder.jeet@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