httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rahul <ra...@Sun.COM>
Subject Re: dtrace patches.
Date Fri, 19 Sep 2008 08:45:13 GMT
Pinging the list once again,

    If atleast the below goes in, it would be possible to submit patches
to increase the coverage independently of the build patches. (I would
like to add more coverage in other interesting modules too.)

|     - discussion on dtrace patches by Theo seems to have wound down
|       lately, with only the build steps being problematic.
|     Here is the least that we could do while the conf|build steps are
|     figured out. (so that more probes can be added in the meantime.)
|    1) we need apache_probes.h to be generated from apache_probes.d in all
|     platforms so that the macros AP*ENTRY|RETURN are defined. (For those
|     without dtrace, it needs to be generated by scripts.)
|     the changes in ap_config.h depends only on this.
|    2) ap.d, and apache_probes.d are independent, and could be added to
|     the trunk or left as patches to be integrated once the conf|build steps
|     are finalized..
|    3) The same with changes in each of *.c files, perhaps bugs(enh) with
|     a 'Dtrace' keyword? so that new entries can be added as patches by
|     others.
| Once this is done, we can split the effort into well defined areas, and
| continue in each independently.
| | This is just a followup to a previous mail:
| | 
| |
| | 
| | The apr-utils include mod got immediate uptake.  Thanks Paul!
| | 
| | I didn't see much progress on the rest of it.  How do I got about  
| | guiding through the patch acceptance process?  Or am I dense and it  
| | was indeed committed and I'm just looking in the wrong place.

1. e4 _

View raw message