All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Waitz <tali@admingilde.org>
To: tony osborne <tonyosborne_a@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OS I/O operations concepts
Date: Thu, 16 Dec 2004 09:25:50 +0100	[thread overview]
Message-ID: <20041216082550.GL31835@admingilde.org> (raw)
In-Reply-To: <BAY14-F1340F1BEA5470EBDE3DD2095AD0@phx.gbl>

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

hoi :)

On Wed, Dec 15, 2004 at 09:10:03PM +0000, tony osborne wrote:
> What about the disk bitmap and the one loaded into the memory. Will this be 
> updated at each Byte write operation? This will slow down extremely the 
> system speed.

no, all data is first written into the buffer cache and will be written
to disk later.

> Should the programmer force the second option (by using BufferOutputStream 
> as in java) or is it done automatically by the JVM or OS?

Writing single bytes can be slow because of another reason:
system calls are expensive and it makes sense to buffer data in the
application and send it to the operating system in one big system call.

> Does the I/O controller (once the device driver installed) full privileges 
> as the main CPU when on kernel mode?

I'm not sure if i understood your question correctly but yes,
The IO Controller has full access to physical memory through DMA.

> is Java system.in.read (system.out.println) synchronous or asynchronous I/O 
> Op

They are synchronous. Otherwise you couldn't access your data at the
moment read() returns.

-- 
Martin Waitz

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-12-16  8:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15 21:10 OS I/O operations concepts tony osborne
2004-12-15 22:54 ` Kyle Moffett
2004-12-16  8:25 ` Martin Waitz [this message]

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=20041216082550.GL31835@admingilde.org \
    --to=tali@admingilde.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tonyosborne_a@hotmail.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 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.