From: Ralf Baechle <ralf@linux-mips.org>
To: "wilbur.chan" <wilbur512@gmail.com>
Cc: Linux MIPS Mailing List <linux-mips@linux-mips.org>,
"Jayachandran C." <jayachandranc@netlogicmicro.com>
Subject: Re: System suffers frequent TLB miss
Date: Tue, 5 Apr 2011 14:21:28 +0200 [thread overview]
Message-ID: <20110405122128.GB31210@linux-mips.org> (raw)
In-Reply-To: <BANLkTikpqk-UcFHHD6MGyZgv6LociaETtg@mail.gmail.com>
On Sun, Apr 03, 2011 at 11:49:13AM +0800, wilbur.chan wrote:
> We have a system running on mips64 xlr 732. Our major application
> process is binded on CPU5,
>
> In order to reduce the tlb miss of our major process, we took the
> following steps:
What page size are you using? If you're still using 4K pages, try switching
to 16K or even 64K pages. You also may want to look into using hugetlbfs.
Ralf
prev parent reply other threads:[~2011-04-05 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-03 3:49 System suffers frequent TLB miss wilbur.chan
2011-04-03 4:07 ` wilbur.chan
2011-04-04 17:42 ` Jayachandran C.
2011-04-05 12:21 ` Ralf Baechle [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=20110405122128.GB31210@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=jayachandranc@netlogicmicro.com \
--cc=linux-mips@linux-mips.org \
--cc=wilbur512@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