This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: array sorting checked in
- From: James Dickens <jamesd dot wi at gmail dot com>
- To: "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: systemtap at sources dot redhat dot com
- Date: Sat, 24 Sep 2005 09:29:07 -0600
- Subject: Re: array sorting checked in
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OlcPJzjMADfQcP4DSCZ7XJ4ciDJ+EQrWaYDyWHjqlGgR6hJg2HxyxDpFINViQ8jVrpONFZpGOniO+Apttk1JTJRULh4m78cYXmUlVhyOtGPPe7d2HLVhs9HGBIJcpgaYdpnlkVagoZlMnps9Q3xWMtOhngMPW4KYj4gRjLBnSO4=
- References: <1127464449.7927.10.camel@dragon> <cd09bdd10509232325619a0e90@mail.gmail.com> <y0my85mhcoc.fsf@tooth.toronto.redhat.com>
- Reply-to: James Dickens <jamesd dot wi at gmail dot com>
[snip]
>
> That is incorrect. If you think about it, you'll see that maintaining
> a sorted array (i.e., at each insert/delete operation) is just about
> as costly as sorting it once at the end. I have no idea what you mean
> by "accuracy" being a factor either way.
>
example you are monitoring a kprobe that fires repeatedly while the
array is being sorted, if you are holding a lock on the array sure you
might block out the first firing of the probe, what happens if it
happens again? or is the system going spin waiting for the lock to be
released or are you going to drop the data from that probe that just
fired?
James
>
> - FChE
>