From: David Howells <dhowells@redhat.com>
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: dhowells@redhat.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Alexander Duyck <alexander.duyck@gmail.com>,
Marc Dionne <marc.dionne@auristor.com>,
Eric Dumazet <edumazet@google.com>,
linux-afs@lists.infradead.org
Subject: Re: [PATCH net] rxrpc: Fix using alignmask being zero for __page_frag_alloc_align()
Date: Fri, 26 Apr 2024 16:57:47 +0100 [thread overview]
Message-ID: <2650223.1714147067@warthog.procyon.org.uk> (raw)
In-Reply-To: <20240422115541.38548-1-linyunsheng@huawei.com>
Yunsheng Lin <linyunsheng@huawei.com> wrote:
> rxrpc_alloc_data_txbuf() may be called with data_align being
> zero in none_alloc_txbuf() and rxkad_alloc_txbuf(), data_align
> is supposed to be an order-based alignment value, but zero is
> not a valid order-based alignment value
Ummm... 0 *would be* a valid order-based[*] alignment (pow(2,0) is 1). It
might actually make more sense to do that than to pass in the number of bytes,
then 0 is the default, but either way works.
[*] Other places that take an order-based parameter include things like
alloc_pages(). The number of pages being requested is pow(2,order).
> + return rxrpc_alloc_data_txbuf(call, min_t(size_t, remain, RXRPC_JUMBO_DATALEN), 1U, gfp);
> + return rxrpc_alloc_data_txbuf(call, space, 1U, gfp);
The 'U' should be unnecessary.
> + data_align = max_t(size_t, data_align, L1_CACHE_BYTES);
data_align = umax(data_align, L1_CACHE_BYTES);
would be better, I think.
Anyway, with the umax change above:
Acked-by: David Howells <dhowells@redhat.com>
prev parent reply other threads:[~2024-04-26 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 11:55 Yunsheng Lin
2024-04-26 8:31 ` Yunsheng Lin
2024-04-26 15:57 ` David Howells [this message]
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=2650223.1714147067@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linyunsheng@huawei.com \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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
all inboxes | Powered by JetHome®