From: "Frank Ch. Eigler" <fche@redhat.com>
To: Martin Hunt <hunt@redhat.com>
Cc: systemtap@sources.redhat.com
Subject: Re: RFC: major runtime map changes
Date: Thu, 20 Oct 2005 17:55:00 -0000 [thread overview]
Message-ID: <20051020175506.GB2761@redhat.com> (raw)
In-Reply-To: <1129828225.4047.18.camel@monkey>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
Hi -
hunt wrote:
> > different per-cpu maps will in general have different set of index
> > tuples?
>
> The per-cpu maps are first aggregated into one map.
>
> Creating a pmap will actually create N+1 maps where N = number of cpus.
> The extra map will be the aggregation map. When _stp_pmap_start(),
> stp_pmap_print(), or _stp_pmap_sort() are called, the per-cpu maps are
> summed into the aggregation map. [...]
OK. Maybe it will be useful to avoid such copying, and do it
virtually, something like this:
- for pmap->lookup(key) iterate over map[cpu]->lookup(key) and aggregate
on the fly
- for iteration, iterate over map[0], aggregating same keys over
map[1..N], then follow that with an iteration over map[1] that skips
those key tuples already handled for map[0], and so on. The
complexity of this may not be smaller than plain merge-then-iterate,
but would eliminate data copying.
- for sorted iteration, sort each map[cpu], then do per-step
"external merge"
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-20 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 22:36 Martin Hunt
2005-10-20 15:49 ` Frank Ch. Eigler
2005-10-20 17:15 ` Martin Hunt
2005-10-20 17:55 ` Frank Ch. Eigler [this message]
2005-10-20 18:20 ` Martin Hunt
2005-10-26 1:08 ` Frank Ch. Eigler
2005-10-26 8:40 ` Martin Hunt
2005-10-20 17:53 ` Martin Hunt
2005-10-20 17:57 ` Frank Ch. Eigler
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=20051020175506.GB2761@redhat.com \
--to=fche@redhat.com \
--cc=hunt@redhat.com \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).