All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 219027] The SCSI can't adjust Max xfer length (blocks) with different storage device
Date: Mon, 05 Aug 2024 12:46:20 +0000	[thread overview]
Message-ID: <bug-219027-11613-d7vPCpAM0I@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219027-11613@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219027

--- Comment #5 from LXY (983292588@qq.com) ---
(In reply to imyxh from comment #4)
> I stumbled across the same issue with an oscilloscope I bought and am just
> writing to say that I needed to set max_sectors under the scsi subsystem,
> not max_sectors_kb under the block subsystem. Even with max_sectors_kb set
> really small, I was seeing read(10) commands for 240 blocks on Wireshark.
> 
> LXY, you wouldn't happen to be developing firmware for FNIRSI, would you? :)

What a pity. I still haven't found a solution.

And I haven't developed firmware for FNIRSI. I'm developing TI's firmware. Just
for my interests.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-08-05 12:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11  2:21 [Bug 219027] New: The SCSI can't adjust Max xfer length (blocks) with different storage device bugzilla-daemon
2024-07-23  1:10 ` [Bug 219027] " bugzilla-daemon
2024-07-23  1:56 ` bugzilla-daemon
2024-07-23  1:57 ` bugzilla-daemon
2024-08-04  4:38 ` bugzilla-daemon
2024-08-05 12:46 ` bugzilla-daemon [this message]
2024-08-05 19:28 ` bugzilla-daemon
2024-08-06  2:16 ` bugzilla-daemon

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=bug-219027-11613-d7vPCpAM0I@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.