4 ms·
And yet it exists, and works gloriously: http://symas.com/mdb/doc/ http://symas.com/mdb/doc/ The kernel is smarter than your app. Trying to force it to do some
by striking 11y ago
And yet it exists, and works gloriously: http://symas.com/mdb/doc/ http://symas.com/mdb/doc/
The kernel is smarter than your app. Trying to force it to do something it doesn't want to do is a very bad idea.
- mveety 11y agoKernels generally aren't all that smart. They're usually dumb and simple programs that do things based on some average defaults that look okay and might work for most people. The kernel needs to be told what to do especially if data integrity is important. Like if some dude thought it was a great idea to store up writes and do them in large transactions and you're writing a filesystem that needs verifiable writes, you turn that off or force it off if you can't disable it otherwise. Relying on the utter sausage factory that is your average kernel is a recipe for disaster. That is especially true for Linux in my experience.
- striking 11y agoI said the kernel is smarter than your app, not psychic. Of course you need to tell Linux what to do with specialized applications. However, any option worth disabling can be disabled. Nothing needs to be forced off like the writer of the article did. mmap'd writes should be flushed as soon as possible, not dragged out, especially in the SSD age we have today. What the writer did was actually counterintuitive and makes no sense. None.
- marssaxman 11y agoThe kernel does have access to more information than your app, but your app has a specific job to do, while the kernel must provide reasonable service to all possible applications and may not be optimized for your specific case.