From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Thomas S. Iversen" <zensonic@zensonic.dk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How to do IO across hardsector boundries
Date: Sun, 01 Aug 2004 00:32:07 +0100 [thread overview]
Message-ID: <1091316727.7486.23.camel@localhost.localdomain> (raw)
In-Reply-To: <410C37B7.3010504@zensonic.dk>
On Sul, 2004-08-01 at 01:22, Thomas S. Iversen wrote:
> So my question really is, how do I go about updating for instance the
> 512 bytes located for at byte 64 to 64+511 on the actual media without
> getting in trouble regarding the data from offset 0-63 and 64+512->1023?
If you want to use the BIO layer then you need to read the two blocks,
write to the bits you care about and then write them back. That is what
will always have to happen at a lower level for this anyway. In essence
you would be implementing the small g_read/g_write equivalent routines.
next prev parent reply other threads:[~2004-08-01 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-01 0:22 How to do IO across hardsector boundries Thomas S. Iversen
2004-07-31 23:32 ` Alan Cox [this message]
2004-08-01 8:53 ` Arjan van de Ven
2004-08-01 13:10 ` Richard B. Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1091316727.7486.23.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zensonic@zensonic.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox