Messages in this thread | | | Subject | Re: [ProbableSpam] Re: [RFC, PATCH 0/5] Going forward with Resource Management - A cpu controller | From | Rohit Seth <> | Date | Mon, 07 Aug 2006 11:19:58 -0700 |
| |
On Mon, 2006-08-07 at 10:15 -0700, Paul Jackson wrote: > > we have a /proc which is very convenient for use from shell etc. but > > is not good for applications, not fast enough etc. > > moreover, /proc had always problems with locking, races and people tend to > > feel like they can change text presention of data, while applications parsing > > it tend to break. > > Yes - one can botch a file system API. > > One can botch syscalls, too. Do you love 'ioctl'? > > For some calls, the performance of a raw syscall is critical. And > eventually, filesystem API's must resolve to raw file i/o syscalls. > > But for these sorts of system configuration and management, the > difference in performance between file system API's and raw syscall > API's is not one of the decisive issues that determines success or > failure. > > Getting a decent API that naturally reflects the long term essential > shape of the data is one of these decisive issues. >
Absolutely. Performance is really not a key here. Setting-up (or Tearing down) these operations shouldn't be that frequent. Configfs (or proc) should be able to handle those.
-rohit
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |