On Wed, 2005-03-30 at 20:25 +1000, Herbert Xu wrote: > Paul Jackson <[email protected]> wrote: > > > > So I suppose if fork_connector were not used to collect <parent pid, > > child pid> information for accounting, then someone would have to make > > the case that there were enough other uses, of sufficient value, to add > > fork_connector. We have to be a bit careful, in the kernel, to avoid > > adding mechanisms until we have the immediate use in hand. If we don't > > do this, then the kernel ends up looking like the Gargoyles on a > > Renaissance church - burdened with overly ornate features serving no > > earthly purpose. > > I agree completely. In fact the whole drivers/connector directory > looks pretty suspect. Are there any in-kernel users of it at all? SuperIO subsystem. In agenda sit w1, acrypto [but it already looks like it will not be included :) ]. -- Evgeniy Polyakov Crash is better than data corruption -- Arthur Grabowski
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- Re: [patch 1/2] fork_connector: add a fork connector
- From: Herbert Xu <[email protected]>
- Re: [patch 1/2] fork_connector: add a fork connector
- Prev by Date: Re: [PATCH 1/6] freepgt: free_pgtables use vma list
- Next by Date: Re: [patch 1/2] fork_connector: add a fork connector
- Previous by thread: Re: [patch 1/2] fork_connector: add a fork connector
- Next by thread: Re: [patch 1/2] fork_connector: add a fork connector
- Index(es):