mo...@rodents-montreal.org (Mouse) writes:
things. What I care about is the largest size sector that will (in
^^^
the ordinary course of things anyway) be written atomically.
Then those are 512-byte-sector drives [...]
No; because I can do 4K atomic
Alan Barrett a...@netbsd.org wrote:
The fexecve function could be implemented entirely in libc,
via execve(2) on a file name of the form /proc/self/fd/N.
Any security concerns around fexecve() also apply to exec of
/proc/self/fd/N.
I gave a try to this approach. There is an unexpected
I could find out myself by digging through the source, but probabely someone
here knows the answer off his head:
When FFS does write coalescing, will it try to align the resulting 64k chunk?
I.e., if I have 32k blocks and I write blocks 1, 2, 3, 4; will it write (1,2)
and (3,4) or 1, (2,3) and 4?
On Mon, Dec 03, 2012 at 06:21:30PM +0100, Edgar Fu? wrote:
When FFS does write coalescing, will it try to align the resulting 64k chunk?
I.e., if I have 32k blocks and I write blocks 1, 2, 3, 4; will it write (1,2)
and (3,4) or 1, (2,3) and 4?
Of course, the background for my question is RAID
On Mon, Dec 03, 2012 at 06:21:30PM +0100, Edgar Fu wrote:
I could find out myself by digging through the source, but probabely someone
here knows the answer off his head:
When FFS does write coalescing, will it try to align the resulting 64k chunk?
I.e., if I have 32k blocks and I write blocks
On Mon, 03 Dec 2012, Chuck Silvers wrote:
the genfs code also never writes clean pages to disk, even though for
RAID5 storage it would likely be more efficient to write clean pages
that are in the same stripe as dirty pages if that would avoid issuing
partial-stripe writes. (which is basically
