From: "joshua dot i dot stone at intel dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/2149] check return value for _stp_map_set_xx()
Date: Thu, 12 Jan 2006 20:49:00 -0000 [thread overview]
Message-ID: <20060112204939.11458.qmail@sourceware.org> (raw)
In-Reply-To: <20060112181937.2149.hunt@redhat.com>
------- Additional Comments From joshua dot i dot stone at intel dot com 2006-01-12 20:49 -------
I don't want to belittle the importance of checking return values, but filled
maps could be avoided by turning on map->wrap. Perhaps we need pragmas or
something to let the user turn this on...
And BTW - the current replacement policy when wrapping is LRU. But, when
aggregating pmaps (_stp_pmap_agg), it favors data from the later cpus in the
for_each_cpu. I'm not sure of a "fair" way to correct this, except to let the
pmap->agg have more entries (MAXMAPENTRIES*NUM_CPUS).
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2149
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2006-01-12 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 18:19 [Bug translator/2149] New: " hunt at redhat dot com
2006-01-12 20:49 ` joshua dot i dot stone at intel dot com [this message]
2006-01-12 20:56 ` [Bug translator/2149] " joshua dot i dot stone at intel dot com
2006-01-12 21:07 ` hunt at redhat dot com
2006-01-16 15:57 ` fche at redhat dot com
2006-01-16 18:23 ` hunt at redhat dot com
2006-04-23 4:32 ` eteo at redhat dot com
2006-04-27 16:46 ` fche at redhat dot com
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=20060112204939.11458.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--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).