Yes.(2) Is my argument about NPTL vs. linuxthreads correct?
I don't think any standard linux distro writes to disk more often than any other linux.(1) Is his argument about linux writing often to main file system correct?
Yes.(2) Is my argument about NPTL vs. linuxthreads correct?
I don't think any standard linux distro writes to disk more often than any other linux.(1) Is his argument about linux writing often to main file system correct?
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
re: linux writing to disk: I read a little while ago that because linux, like all *nix, maintains "access times" for the filesystem, this means every disk read must also be complimented by a disk WRITE in order to update the atime. Supposedly all this adds up, so in heavy use situations where the atime is not considered crucial (since the m(odification)time is seperate from the atime, you might wonder when it ever would really be important) you can start linux with the "noatime" kernel parameter which means the kernel no longer writes an atime to disk every time a file is accessed. And this means something like a 10-20% improvement in speed where the disk access is constant.
Since you are dealing with significance on the order of 25ms and are worried about time wasted with (basically irrelevent) writes to disk, I thot I'd mention that. Google "noatime" and some articles will appear.
C programming resources:
GNU C Function and Macro Index -- glibc reference manual
The C Book -- nice online learner guide
Current ISO draft standard
CCAN -- new CPAN like open source library repository
3 (different) GNU debugger tutorials: #1 -- #2 -- #3
cpwiki -- our wiki on sourceforge
I apologize I was not detailed and precise:
actually his complete argument is that his embedded linux has the main file system on ramdisk and only a subdir as flash
This would eliminate compact flash progressive corruption (still actually I guess reached in so many years it is not very relevant) and would reduce the time loss
But I remember I made some tests on Debian with RAMdisk and I found out that the time for writing to ramdisk was only 20% less than writing on hard disk
Plus as I said our applications would write so little that the compact flash would be corrupted in xxx years so..
Yes, Linux is generally using any spare memory (memory that isn't currently used by applications or the kernel itself) as a cache for disk operations, so writing to disk will actually just write to memory, and later on write to disk proper.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.