cvs commit: src/sys/conf files options src/sys/kern kern_rwlock.c subr_lock.c src/sys/sys lock.h rwlock.h

[Peter Jeremy]

On Tue, 2006-Jan-31 19:07:05 +0000, Robert Watson wrote:
>On Tue, 31 Jan 2006, John Baldwin wrote:
>>>Can I suggest that this module be committed into tools/regression or
>>>similar so that it is generally available.
>>
>>I can I guess.  I have 3 currently (crash, evtest, and crash2 (which is 
>>the latest one that uses multiple threads, crash just has a single 
>>thread)).

I'm not trying to push John to release code that he is unhappy with.
I just think the code could potentially be useful to other people in
the future.

>It would be nice of we had something on the order of src/sys/test, where we 
>could put test kernel code that is never intended to see production.

I suggested tools/regression because that seemed to be the most suitable
existing directory (src/sys/tools is used for build tools).  src/sys/test
or some sub-directories in src/sys/tools would be better.

>  The 
>problem with putting things in src/tools is that the code gets very stale, 
>very quickly, as kernel APIs move and the implementation in that tree 
>doesn't.

I'm not sure that putting tools into sys would help here.  It's
unreasonable to expect a developer to expend effort in updating some
tools that he created several years ago to assist with some testing
but isn't actively using.  Likewise, it's difficult to insist that
another developer provide updates to tools that he's never used and
that aren't part of the production kernel.

-- 
Peter Jeremy