From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [patch] cdfs handle block sizes correctly
Date: Sun, 02 Oct 2022 16:04:41 -0400 [thread overview]
Message-ID: <A1DBB7B503ADD7D8261D0224D8B23553@eigenstate.org> (raw)
In-Reply-To: <1993373294.3416290.1664736998610@comcenter.netcologne.de>
Quoth Arne Meyer <meyer.arne83@netcologne.de>:
> 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.
next prev parent reply other threads:[~2022-10-02 20:06 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 [this message]
2022-10-22 16:20 ` Arne Meyer
2022-10-22 18:43 ` ori
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=A1DBB7B503ADD7D8261D0224D8B23553@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/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;
as well as URLs for NNTP newsgroup(s).