From: Greg KH <gregkh@linuxfoundation.org>
To: Hardeep Sharma <quic_hardshar@quicinc.com>
Cc: Jens Axboe <axboe@kernel.dk>, Hannes Reinecke <hare@suse.de>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 6.6.y v2 1/1] block: Fix bounce check logic in blk_queue_may_bounce()
Date: Thu, 14 Aug 2025 15:54:35 +0200 [thread overview]
Message-ID: <2025081404-conceal-next-8858@gregkh> (raw)
In-Reply-To: <4a898590-e1ca-41dc-b8b7-a5884d10db5d@quicinc.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Aug 14, 2025 at 06:36:29PM +0530, Hardeep Sharma wrote:
> This change to blk_queue_may_bounce() in block/blk.h will only affect
> systems with the following configuration:
>
> 1. 32-bit ARM architecture
> 2. Physical DDR memory greater than 1GB
> 3. CONFIG_HIGHMEM enabled
> 4. Virtual memory split of 1GB for kernel and 3GB for userspace
>
> Under these conditions, the logic for buffer bouncing is relevant because
> the kernel may need to handle memory above the low memory threshold, which
> is typical for highmem-enabled 32-bit systems with large RAM. On other
> architectures or configurations, this code path will not be exercised.
You did not answer most of the questions I asked for some reason :(
next prev parent reply other threads:[~2025-08-14 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 6:36 [PATCH 6.6.y v2 1/1] block: Fix bounce check logic in blk_queue_may_bounce() Hardeep Sharma
2025-08-14 9:03 ` Greg KH
2025-08-14 10:54 ` Hardeep Sharma
2025-08-14 11:36 ` Greg KH
2025-08-14 13:06 ` Hardeep Sharma
2025-08-14 13:54 ` Greg KH [this message]
2025-08-14 13:11 ` Hardeep Sharma
-- strict thread matches above, loose matches on Subject: below --
2025-07-25 11:27 Hardeep Sharma
2025-07-25 12:04 ` Greg KH
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=2025081404-conceal-next-8858@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=quic_hardshar@quicinc.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox