Bug 3539 - Evaluate proc.getParent lazy style
Summary: Evaluate proc.getParent lazy style
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
Depends on: 3873
Blocks: 1593
  Show dependency treegraph
Reported: 2006-11-17 21:29 UTC by Andrew Cagney
Modified: 2007-01-25 22:11 UTC (History)
0 users

See Also:
Last reconfirmed:

patch to implement a getProc interface, (4.48 KB, patch)
2007-01-15 20:43 UTC, Nurdin Premji
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2006-11-17 21:29:55 UTC
Instead of populating a Proc's parent during creation, populate it on-demand.

This will reduce the number of processes created on a very large system down to
those that are needed.
Comment 1 Nurdin Premji 2007-01-10 20:33:25 UTC
I think I have a working interface set up for this, however the testsuite uses
the function isChildOfMine() for the purposes of teardown which requires an
existing parent so this would effectively require each proc to have a parent.

I think this is a throwback to the requestRefreshXXX code,which is mostly gone
but there are still some tests using it.
Comment 2 Nurdin Premji 2007-01-15 20:43:17 UTC
Created attachment 1498 [details]
patch to implement a getProc interface,