From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Dave Jones'" <davej@redhat.com>
Cc: "'Zach Brown'" <zach.brown@oracle.com>,
"'Suparna Bhattacharya'" <suparna@in.ibm.com>,
"Lahaise, Benjamin C" <benjamin.c.lahaise@intel.com>,
<linux-kernel@vger.kernel.org>, "linux-aio" <linux-aio@kvack.org>
Subject: RE: [patch] rearrange kioctx and aio_ring_info
Date: Thu, 12 Oct 2006 17:20:52 -0700 [thread overview]
Message-ID: <000401c6ee5d$727de3e0$db34030a@amr.corp.intel.com> (raw)
In-Reply-To: <20061013000347.GA8673@redhat.com>
Dave Jones wrote on Thursday, October 12, 2006 5:04 PM
> On Thu, Oct 12, 2006 at 04:25:54PM -0700, Chen, Kenneth W wrote:
> > The following patch is result of our kernel data latency analysis on a
> > large database setup (128 logical CPU, 1 TB memory, a couple thousand
> > disks). The analysis is done at an individual cache line level through
> > hardware performance monitor unit. What we did essentially is to collect
> > data access latency on every kernel memory address and look for top 50
> > longest average access latency. The hardware performance unit also keeps
> > track of instruction address for each collected data access. This allows
> > us to further associate each of the top 50 cache lines to instruction
> > sequences that caused long latency.
>
> Do you have performance numbers of before/after this change ?
Not yet, I just queued up experiment on our internal benchmark setup. I posted
the patch here to get some early discussion on how to attack the problem.
prev parent reply other threads:[~2006-10-13 0:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 23:25 Chen, Kenneth W
2006-10-12 23:38 ` Zach Brown
2006-10-12 23:41 ` Zach Brown
2006-10-13 0:03 ` Dave Jones
2006-10-13 0:20 ` Chen, Kenneth W [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='000401c6ee5d$727de3e0$db34030a@amr.corp.intel.com' \
--to=kenneth.w.chen@intel.com \
--cc=benjamin.c.lahaise@intel.com \
--cc=davej@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suparna@in.ibm.com \
--cc=zach.brown@oracle.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
all inboxes | Powered by JetHome®