This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi -Ok, so let me see if I understand the idea. In this model the calling app
On Wed, Sep 15, 2010 at 01:11:55PM +1000, Greg Banks wrote:
Re Frank's API proposal: how does the client cancel a watch?
In the pmWatch idea, control is handed to pmapi during the watch
interval. The client receives callbacks periodically, and at those
times, it has the chance to cancel the watch. This is what the
poll/timeout intervals were for: to guarantee that the client will get
some sort of callback no less frequently than the requested
interval(s).
What thread is doing the servicing of the socket to PMCD, and if the
main app thread, when?
It would be the single pmapi/app thread.
If one puts the burden of buffering and client-state-keeping onto a PMDA, probably the same flavour of scheme can work there too, with single-threaded polling.
-- Greg.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |