public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
* drop "task" refresh?
@ 2007-05-22 15:31 Andrew Cagney
  2007-05-22 15:58 ` Phil Muldoon
  0 siblings, 1 reply; 3+ messages in thread
From: Andrew Cagney @ 2007-05-22 15:31 UTC (permalink / raw)
  To: frysk

Hello,

Frysk's code that scans and refreshes from /proc can perform the 
operation either at the process or the more expensive task level.  In 
examining the various interfaces presented to users, I'm questioning how 
useful the "task" level scan is; I suspect it is being enabled through 
copy-paste only.

For instance, the process-picker only ever displays processes and the 
command line only ever lets the user specify a process.  Yet those 
methods seem to be doing task-level scans of /proc.

thoughts?

Andrew

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: drop "task" refresh?
  2007-05-22 15:58 ` Phil Muldoon
@ 2007-05-22 15:32   ` Andrew Cagney
  0 siblings, 0 replies; 3+ messages in thread
From: Andrew Cagney @ 2007-05-22 15:32 UTC (permalink / raw)
  To: Phil Muldoon; +Cc: frysk

Hi Phil,

Phil Muldoon wrote:
> Andrew Cagney wrote:
>> Hello,
>>
>> Frysk's code that scans and refreshes from /proc can perform the 
>> operation either at the process or the more expensive task level.  In 
>> examining the various interfaces presented to users, I'm questioning 
>> how useful the "task" level scan is; I suspect it is being enabled 
>> through copy-paste only.
>>
>> For instance, the process-picker only ever displays processes and the 
>> command line only ever lets the user specify a process.  Yet those 
>> methods seem to be doing task-level scans of /proc.
>
> I guess I'll answer with a question of my own back:
>
me too :-)

> If you do a "top-level" (no tasks) refresh, and you do a 
> Proc.getTasks() what will that return?

That's a good question.  Is there only a problem with a "live" process 
though, and there the refresh ends up being on-demand when synchronizing 
the task set during an attach.

Anyway, for either case, yes I agree, it can be pushed into the lower 
level code.

W.r.t. the ABI, should it be restricted to Proc/Tasks that are 
"blocked"?  Of course for corefiles all tasks are "blocked" :-)

Andrew



>
> If it does an "on-demand" task refresh, then I would say yes, dump the 
> task level refresh option and make the api internal.
>
> If not, and it is just returning the results from the taskPool from 
> the  last "deep" refresh, then maybe we need to rethink both refresh 
> and get{Main}Task{s}() api?
>
> Regards
>
> Phil
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: drop "task" refresh?
  2007-05-22 15:31 drop "task" refresh? Andrew Cagney
@ 2007-05-22 15:58 ` Phil Muldoon
  2007-05-22 15:32   ` Andrew Cagney
  0 siblings, 1 reply; 3+ messages in thread
From: Phil Muldoon @ 2007-05-22 15:58 UTC (permalink / raw)
  To: Andrew Cagney; +Cc: frysk

Andrew Cagney wrote:
> Hello,
>
> Frysk's code that scans and refreshes from /proc can perform the 
> operation either at the process or the more expensive task level.  In 
> examining the various interfaces presented to users, I'm questioning 
> how useful the "task" level scan is; I suspect it is being enabled 
> through copy-paste only.
>
> For instance, the process-picker only ever displays processes and the 
> command line only ever lets the user specify a process.  Yet those 
> methods seem to be doing task-level scans of /proc.

I guess I'll answer with a question of my own back:

If you do a "top-level" (no tasks) refresh, and you do a Proc.getTasks() 
what will that return?

If it does an "on-demand" task refresh, then I would say yes, dump the 
task level refresh option and make the api internal.

If not, and it is just returning the results from the taskPool from the  
last "deep" refresh, then maybe we need to rethink both refresh and 
get{Main}Task{s}() api?

Regards

Phil

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-05-22 15:32 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-05-22 15:31 drop "task" refresh? Andrew Cagney
2007-05-22 15:58 ` Phil Muldoon
2007-05-22 15:32   ` Andrew Cagney

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).