public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josue Emmanuel Amaro <Josue.Amaro@oracle.com>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Value of TASK_UNMAPPED_SIZE on 2.4
Date: Fri, 03 Nov 2000 23:39:52 -0800	[thread overview]
Message-ID: <3A03BD47.4FBD876B@oracle.com> (raw)
In-Reply-To: <3A030EE2.92DC3F2@oracle.com>

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

All,

Additional follow up.

The idea of modifying this variable is to increase the amount of memory that a
process can use.  A database like Oracle can benefit from this because it allows
Oracle to create a bigger data buffer.

An obvious side effect of allocating more physical memory to a process is that there
is less available for other things like the kernel buffer cache.  This brings up a
question.  Would a write of a data block from the Oracle data buffer incur a "read
penalty" if the block is not in the buffer cache?

For example, a data block is read by Oracle into its buffer.  Since it is read
through the file system, this block is now present in the buffer cache too.  After a
while, and since we have allocated most of the memory to Oracle, that block is
removed/replaced from the cache.

Now a transaction modifies that block in Oracle's buffer and Oracle writes it to
disk.  Does the kernel firsts reads that block into the buffer cache, "read
penalty", and then writes it to disk? Or does it just write through the buffer cache
now placing the block in the kernel buffer cache?

Regards,

--
=======================================================================
  Josue Emmanuel Amaro                         Josue.Amaro@oracle.com
  Linux Products Manager                       Phone:   650.506.1239
  Intel and Linux Technologies Group           Fax:     650.413.0167
=======================================================================


[-- Attachment #2: Card for Josue Emmanuel Amaro --]
[-- Type: text/x-vcard, Size: 390 bytes --]

begin:vcard 
n:Amaro;Josue Emmanuel
tel;cell:650-245-5131
tel;fax:650-413-0167
tel;work:650-506-1239
x-mozilla-html:FALSE
url:http://www.oracle.com
org:Intel and Linux Technologies
version:2.1
email;internet:Josue.Amaro@oracle.com
title:Sr.Product Manager - Linux
adr;quoted-printable:;;500 Oracle Parkway=0D=0AMS1ip4;Redwood Shores;CA;94065;United States
fn:Josue Emmanuel Amaro
end:vcard

  parent reply	other threads:[~2000-11-04  7:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-03 19:15 Value of TASK_UNMAPPED_SIZE on 2.4 Josue Emmanuel Amaro
2000-11-03 19:37 ` Andrea Arcangeli
2000-11-04  7:39 ` Josue Emmanuel Amaro [this message]
     [not found] <fa.d4dt9vv.1gm6abv@ifi.uio.no>
     [not found] ` <fa.ebii26v.1mgevrq@ifi.uio.no>
2000-11-03 20:27   ` Kai Harrekilde-Petersen
2000-11-03 20:46     ` Andrea Arcangeli
2000-11-03 22:36       ` Josue Emmanuel Amaro
2000-11-20  2:09         ` Andrea Arcangeli
  -- strict thread matches above, loose matches on Subject: below --
2000-11-04  1:09 Julian Anastasov
2000-11-04  0:51 ` Andrea Arcangeli
2000-11-04 10:37   ` Julian Anastasov

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=3A03BD47.4FBD876B@oracle.com \
    --to=josue.amaro@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    /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