Subject: Re: [9front] [patch] cdfs handle block sizes correctly
Date: Sat, 22 Oct 2022 14:43:44 -0400 [thread overview]
Message-ID: <7F86E63878E74D4F63D07F90BA8822A5@eigenstate.org> (raw)
Quoth Arne Meyer <email@example.com>:
> > firstname.lastname@example.org hat am 02.10.2022 20:04 GMT geschrieben:
> > Quoth Arne Meyer <email@example.com>:
> > > The old Readblock value is fine for data tracks, because 4 2048 byte blocks fit in the 8192 byte RPCMAX. But cdda blocks are 2352 bytes and 4 of those don't fit into 8192 bytes and stuff breaks. If I read the code correctly my change should set the number of blocks to 4 for data tracks and to 3 for everything else.
> > Ah, I misunderstood you -- I thought you were saying you had disks
> > where the blocksize was larger than RPCMAX (8k).
> > I'll take another look.
ponged and applied; thanks!
prev parent reply other threads:[~2022-10-22 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 10:34 Arne Meyer
2022-10-01 21:20 ` ori
2022-10-02 18:56 ` Arne Meyer
2022-10-02 20:04 ` ori
2022-10-22 16:20 ` Arne Meyer
2022-10-22 18:43 ` ori [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).