christos@nyc.deshaw.com (Christos Zoulas) writes:

> Maybe proc0 could used in that case?

Do you mean kernel process?  Anyway it should be done in upper half of
kernel if it needs to be done in kernel.  But if writes accounting
data through nfs, the write (and disk capacity check itself) may block
long time.  So, there needs a mechanizm to suspend accounting in such
case, otherwise many process may wait during writing accounting data.

> Problems like buffering when the user space reader dies, or
> resynchronization of the data.

Even if we accept to lose some data?  If we try not to lose any data,
they may be problems.  But, with current implementation, accounting
data is lost when accounting is suspended, isn't it?

Probably if some part of accounting task is moved to user space, the
chance to lose data may increase.

enami