DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=lptzKIw
	ur0o6P3hj2e1tCVZQaNYKzHeE1b0Mikv4sMnkw1fuJvNl0p+aXhQLoxFivEExj+G
	ag6DIdMiXaICBLn2jc2xIXf7Uj6Sf6FYYp18pj5Ay09aocSOfjdrip5tRobTE781
	OwnYtG81VL5jJZ0GFqCtTX+kklBNkFnIig3o=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <9f29d418-10af-1dc7-2636-89cae1eb16f4@redhat.com>
References: <20171218131035.GB11285@calimero.vinschen.de> <5a385ced.195b9d0a.d434.5400@mx.google.com> <20171219091431.GF11285@calimero.vinschen.de> <CAKyntiLyTBGcAx3iwhq7dX0wqiE3S685kwmhMg+U2A3huXVzUQ@mail.gmail.com> <9f29d418-10af-1dc7-2636-89cae1eb16f4@redhat.com>
From: Ivan Kozik <ivan@ludios.org>
Date: Tue, 19 Dec 2017 16:35:21 +0000
Message-ID: <CAKyntiLJTjk+5Qs0jAjxAUPJTzfY4R57GRaQjZLwBBeuMM++0Q@mail.gmail.com>
Subject: Re: Wrong file position after writing 65537 bytes to block device
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

On Tue, Dec 19, 2017 at 4:13 PM, Eric Blake <eblake@redhat.com> wrote:
> Can block devices report an unaligned offset to lseek()?  If not, then when
> writing an unaligned value to a block device, don't we have to do a
> read-modify-write of the larger aligned cluster, and then put lseek() back
> to the unaligned boundary, and have extra magic in ftell() to track that we
> are at an unaligned position within the block device?  But that sounds like
> a lot of nasty overhead; and that it would be better to make sure that block
> devices can report unaligned lseek() locations (caveat: I haven't tested
> what Linux does in that regards).

From what I observe on Linux, it supports writing at any offset to the
block device because it does a read-modify-write behind the scenes,
with accompanying nasty overhead (e.g. writes going at 64MB/s instead
of an "expected" 180MB/s).

I think you can observe this behavior on Linux by piping this
program's stdout to a block device (note: must be python3, not
python2):

#!/usr/bin/python3

import sys

block = b" " * 4096
while True:
    sys.stdout.buffer.write(block)
    sys.stdout.buffer.write(b" ")

and watching the block device activity with `dstat -d -D sdN` - you
should see a lot of reads.

Ivan

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple