From: "Martin J. Bligh" <mbligh@aracnet.com>
To: "Luck, Tony" <tony.luck@intel.com>,
Andrew Morton <akpm@digeo.com>, Peter Wong <wpeter@us.ibm.com>
Cc: linux-mm@kvack.org, lse-tech@lists.sourceforge.net,
riel@nl.linux.org, wli@holomorphy.com, dmccr@us.ibm.com,
gh@us.ibm.com, Bill Hartner <bhartner@us.ibm.com>,
Troy C Wilson <wilsont@us.ibm.com>
Subject: RE: [Lse-tech] Re: Examining the Performance and Cost of Revesema ps on 2.5.26 Under Heavy DBWorkload
Date: Tue, 17 Sep 2002 14:42:31 -0700 [thread overview]
Message-ID: <129560000.1032298951@flay> (raw)
In-Reply-To: <39B5C4829263D411AA93009027AE9EBB13299719@fmsmsx35.fm.intel.com>
>> > That's a ton of memory. Where do we stand wrt getting these
>> > applications to use large-tlb pages?
>>
>> We need standard interfaces (like shmem) to get DB2 to port, and probably
>> most other applications. Having magic system calls is all very well in
> theory,
>> but not much use in practice.
>>
>> And yes, we're still working on it.
>
> Can't you use LD_PRELOAD tricks to sneak a different version shmget/shmat
> to your DB2 binary so that you can intercept the important calls and
> divert them to use huge tlb pages?
If we had a shmget/shmat call that supported large pages, that would
probably make it easier ? ;-) That's the whole issue - large pages aren't
supported with standard syscalls, so every app is required to rewrite their
memory handling, which isn't going to happen.
M.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-09-17 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 21:22 [Lse-tech] Re: Examining the Performance and Cost of Revesema ps on 2.5.26 Under Heavy DBWorkload Luck, Tony, Martin
2002-09-17 21:42 ` Martin J. Bligh [this message]
2002-09-17 21:47 ` William Lee Irwin III
2002-09-17 21:58 ` Martin J. Bligh
2002-09-17 22:49 ` Hubertus Franke
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=129560000.1032298951@flay \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--cc=bhartner@us.ibm.com \
--cc=dmccr@us.ibm.com \
--cc=gh@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=riel@nl.linux.org \
--cc=tony.luck@intel.com \
--cc=wilsont@us.ibm.com \
--cc=wli@holomorphy.com \
--cc=wpeter@us.ibm.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.