Application-accessible nvram/cache for Linux?

Michael ODonnell michael.odonnell at comcast.net
Fri Jun 22 14:40:11 EDT 2007



>> after *each* write to memory.  Nothing that's yet been mentioned
>> here will yield that sort of behavior.  I suppose it would be
>> possible to simulate it by (say) marking the region of memory
>> in question as Read Only and then having the SEGFAULT handler
>> update the corresponding block on the device, but...  ick!
>
> I was taking about using it with a flash device.  If you utilize
> O_DIRECT, your write will occur directly to the device, in this
> case, written to flash.

(sigh) I have to get back to work, so one last try:

   You're confused about O_DIRECT.  It just specifies that
   that the data not go into the buffer cache when the write()
   syscall is invoked.

   We're talking about "writes to memory" not write() syscalls.
 


More information about the gnhlug-discuss mailing list