From: Martin Hunt <hunt@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: "systemtap@sources.redhat.com" <systemtap@sources.redhat.com>
Subject: Re: RFC: major runtime map changes
Date: Thu, 20 Oct 2005 17:53:00 -0000 [thread overview]
Message-ID: <1129830850.8161.6.camel@monkey> (raw)
In-Reply-To: <y0m7jc82npw.fsf@toenail.toronto.redhat.com>
While we're talking about changes to maps, what should happen when an
_stp_map_set_xxx() fails due to lack of space? Currently this does not
happen because maps are set to wrap by default. So the oldest entry in
the map is cleared and reused. There is a BZ asking for that to be
changed.
So which of the following should happen?
1. wraps and returns an error code
2. fails (does not store value) and returns error code
3. increments a "drops" counter for the map
4. does stp_warn()
next prev parent reply other threads:[~2005-10-20 17:53 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
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 [this message]
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=1129830850.8161.6.camel@monkey \
--to=hunt@redhat.com \
--cc=fche@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).