Daniel Phillips wrote:So you apparently want three things: a) ignoring fsync() and co on this device b) disabling all write throttling on this device c) never discarding cached data from this device anything else i'm missing? Alan already suggested the ramfs+writeback thread approach (possibly with a little bit of help from the fs which could report just the dirty regions), but i'm not sure even that is necessary. (a) can be easily done (fixing the app, LD_PRELOAD or fs extension etc) (b) couldn't the per-device write throttling be used to achieve this? (c) shouldn't be impossible either, eg sticking PG_writeback comes to mind, just the mm accounting needs to remain sane. IOW can't this be done in a more generic way (and w/o a ramdisk in the middle)? apples to oranges. what are the numbers for a nonjournalled disk-backed fs and _without_ the sync? (You're not committing to stable storage anyway so the sync is useless and if you don't respect the ordering so is the journal) artur --
| Hiten Pandya | Re: up? (emacs docbook xml ide) |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Ingo Molnar | iwlwifi: fix build bug in "iwlwifi: fix LED stall" |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
