From: Rik van Riel <riel@surriel.com>
To: Rajat Jain <rajat.noida.india@gmail.com>
Cc: idlisambar@gmail.com, kernelnewbies <kernelnewbies@nl.linux.org>,
Linux Newbie <linux-newbie@vger.kernel.org>
Subject: Re: Issuing BIOS interrupts in Linux
Date: Sat, 05 Aug 2006 10:54:44 -0400 [thread overview]
Message-ID: <44D4B134.1070002@surriel.com> (raw)
In-Reply-To: <b115cb5f0608050611qe937318qf04d87a472dc849a@mail.gmail.com>
Rajat Jain wrote:
> Actually I was thinking that if it is possible to perform all the Disk
> IO operations using the BIOS routines, then why can't we write a
> SINGLE disk driver that will work with all the kinds of disks.
Because that would be incredibly slow. You could only have one I/O
request in flight at a time, and the system could not run other
processes while I/O was being done.
> So all this seems like a bad idea ... or should I say TOTALLY IMPOSSIBLE?
It might be possible, but it is still a very bad idea :)
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2006-08-05 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 11:00 Issuing BIOS interrupts in Linux Rajat Jain
2006-08-05 1:20 ` Rahul Iyer
[not found] ` <292693080608050553x756e4276k33c5afa80f686f44@mail.gmail.com>
2006-08-05 13:11 ` Rajat Jain
2006-08-05 14:54 ` Rik van Riel [this message]
2006-08-05 15:26 ` Rajat Jain
2006-08-05 16:33 ` Nilesh Agrawal
2006-08-09 1:50 ` David H. Lynch Jr.
2006-08-09 5:14 ` Rajat Jain
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=44D4B134.1070002@surriel.com \
--to=riel@surriel.com \
--cc=idlisambar@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-newbie@vger.kernel.org \
--cc=rajat.noida.india@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