From: Simon Horman <horms@kernel.org>
To: tianx <tianx@yunsilicon.com>
Cc: netdev@vger.kernel.org, leon@kernel.org, andrew+netdev@lunn.ch,
kuba@kernel.org, pabeni@redhat.com, edumazet@google.com,
davem@davemloft.net, jeff.johnson@oss.qualcomm.com,
przemyslaw.kitszel@intel.com, weihg@yunsilicon.com,
wanry@yunsilicon.com, parthiban.veerasooran@microchip.com,
masahiroy@kernel.org
Subject: Re: [PATCH v4 05/14] net-next/yunsilicon: Add eq and alloc
Date: Mon, 24 Feb 2025 18:58:17 +0000 [thread overview]
Message-ID: <20250224185817.GH1615191@kernel.org> (raw)
In-Reply-To: <b0adf539-8104-452d-ba34-14a120602bd5@yunsilicon.com>
On Thu, Feb 20, 2025 at 11:35:26PM +0800, tianx wrote:
> On 2025/2/19 1:10, Simon Horman wrote:
> > On Thu, Feb 13, 2025 at 05:14:14PM +0800, Xin Tian wrote:
...
> >> diff --git a/drivers/net/ethernet/yunsilicon/xsc/pci/alloc.c b/drivers/net/ethernet/yunsilicon/xsc/pci/alloc.c
> > ...
> >
> >> +/* Handling for queue buffers -- we allocate a bunch of memory and
> >> + * register it in a memory region at HCA virtual address 0. If the
> >> + * requested size is > max_direct, we split the allocation into
> >> + * multiple pages, so we don't require too much contiguous memory.
> >> + */
> > I can't help but think there is an existing API to handle this.
> failed to find one
Yes, me neither.
> >> +int xsc_buf_alloc(struct xsc_core_device *xdev, int size, int max_direct,
> > I think unsigned long would be slightly better types for size and max_direct.
> yes, will modify
> >> + struct xsc_buf *buf)
> >> +{
> >> + dma_addr_t t;
> >> +
> >> + buf->size = size;
> >> + if (size <= max_direct) {
> >> + buf->nbufs = 1;
> >> + buf->npages = 1;
> >> + buf->page_shift = get_order(size) + PAGE_SHIFT;
> >> + buf->direct.buf = dma_alloc_coherent(&xdev->pdev->dev,
> >> + size,
> >> + &t,
> >> + GFP_KERNEL | __GFP_ZERO);
> >> + if (!buf->direct.buf)
> >> + return -ENOMEM;
> >> +
> >> + buf->direct.map = t;
> >> +
> >> + while (t & ((1 << buf->page_shift) - 1)) {
> > I think GENMASK() can be used here.
> ok
> >> + --buf->page_shift;
> >> + buf->npages *= 2;
> >> + }
> >> + } else {
> >> + int i;
> >> +
> >> + buf->direct.buf = NULL;
> >> + buf->nbufs = (size + PAGE_SIZE - 1) / PAGE_SIZE;
> > I think this is open-coding DIV_ROUND_UP
> right, I'll change
> >> + buf->npages = buf->nbufs;
> >> + buf->page_shift = PAGE_SHIFT;
> >> + buf->page_list = kcalloc(buf->nbufs, sizeof(*buf->page_list),
> >> + GFP_KERNEL);
> >> + if (!buf->page_list)
> >> + return -ENOMEM;
> >> +
> >> + for (i = 0; i < buf->nbufs; i++) {
> >> + buf->page_list[i].buf =
> >> + dma_alloc_coherent(&xdev->pdev->dev, PAGE_SIZE,
> >> + &t, GFP_KERNEL | __GFP_ZERO);
> >> + if (!buf->page_list[i].buf)
> >> + goto err_free;
> >> +
> >> + buf->page_list[i].map = t;
> >> + }
> >> +
> >> + if (BITS_PER_LONG == 64) {
> >> + struct page **pages;
> >> +
> >> + pages = kmalloc_array(buf->nbufs, sizeof(*pages),
> >> + GFP_KERNEL);
> >> + if (!pages)
> >> + goto err_free;
> >> + for (i = 0; i < buf->nbufs; i++) {
> >> + void *addr = buf->page_list[i].buf;
> >> +
> >> + if (is_vmalloc_addr(addr))
> >> + pages[i] = vmalloc_to_page(addr);
> >> + else
> >> + pages[i] = virt_to_page(addr);
> >> + }
> >> + buf->direct.buf = vmap(pages, buf->nbufs,
> >> + VM_MAP, PAGE_KERNEL);
> >> + kfree(pages);
> >> + if (!buf->direct.buf)
> >> + goto err_free;
> >> + }
> > I think some explanation is warranted of why the above is relevant
> > only when BITS_PER_LONG == 64.
> Some strange historical reasons, and no need for the check now. I'll
> clean this up
Thanks.
If you do need 64bit only logic, then perhaps it can be moved to a
separate function. It could guard code using something like this.
int some_func(struct xsc_buf *buf)
{
if (!IS_ENABLED(CONFIG_64BIT))
return 0;
...
}
Or if that is not possible, something like this:
#ifdef CONFIG_64BIT
int some_func(struct xsc_buf *buf)
{
...
}
#else /* CONFIG_64BIT */
int some_func(struct xsc_buf *buf) { return 0; }
#fi /* CONFIG_64BIT */
> >> + }
> >> +
> >> + return 0;
> >> +
> >> +err_free:
> >> + xsc_buf_free(xdev, buf);
> >> +
> >> + return -ENOMEM;
> >> +}
> > ...
> >
> >> +void xsc_fill_page_array(struct xsc_buf *buf, __be64 *pas, int npages)
> > As per my comment on unsigned long in my response to another patch,
> > I think npages can be unsigned long.
> ok
> >> +{
> >> + int shift = PAGE_SHIFT - PAGE_SHIFT_4K;
> >> + int mask = (1 << shift) - 1;
> > Likewise, I think that mask should be an unsigned long.
> > Or, both shift and mask could be #defines, as they are compile-time
> > constants.
> >
> > Also, mask can be generated using GENMASK, e.g.
> >
> > #define XSC_PAGE_ARRAY_MASK GENMASK(PAGE_SHIFT, PAGE_SHIFT_4K)
> > #define XSC_PAGE_ARRAY_SHIFT (PAGE_SHIFT - PAGE_SHIFT_4K)
> >
> > And I note, in the (common) case of 4k pages, that both shift and mask are 0.
>
> Thank you for the suggestion, but that's not quite the case here. The
> |shift| and |mask| are not used to extract fields from data. Instead,
> they are part of a calculation. In |xsc_buf_alloc|, we allocate the
> buffer based on the system's page size. However, in this function, we
> need to break each page in the |buflist| into 4KB chunks, populate the
> |pas| array with the corresponding DMA addresses, and then map them to
> hardware.
>
> The |shift| is calculated as |PAGE_SHIFT - PAGE_SHIFT_4K|, allowing us
> to convert the 4KB chunk index (|i|) to the corresponding page index in
> |buflist| with |i >> shift|. The |i & mask| gives us the offset of the
> current 4KB chunk within the page, and by applying |((i & mask) <<
> PAGE_SHIFT_4K)|, we can compute the offset of that chunk within the page.
>
> I hope this makes things clearer!
Thanks, that is clear.
I do still think that the shift and mask could
be compile-time constants rather than local variables.
And it does seem to me that GENMASK can be used to generate the mask.
...
next prev parent reply other threads:[~2025-02-24 18:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 9:14 [PATCH v4 00/14] net-next/yunsilicon: ADD Yunsilicon XSC Ethernet Driver Xin Tian
2025-02-13 9:14 ` [PATCH v4 01/14] net-next/yunsilicon: Add xsc driver basic framework Xin Tian
2025-02-13 9:14 ` [PATCH v4 02/14] net-next/yunsilicon: Enable CMDQ Xin Tian
2025-02-13 9:14 ` [PATCH v4 03/14] net-next/yunsilicon: Add hardware setup APIs Xin Tian
2025-02-13 9:14 ` [PATCH v4 04/14] net-next/yunsilicon: Add qp and cq management Xin Tian
2025-02-18 16:31 ` Simon Horman
2025-02-20 8:58 ` tianx
2025-02-13 9:14 ` [PATCH v4 05/14] net-next/yunsilicon: Add eq and alloc Xin Tian
2025-02-18 17:10 ` Simon Horman
2025-02-20 15:35 ` tianx
2025-02-24 18:58 ` Simon Horman [this message]
2025-02-25 2:34 ` Xin Tian
2025-02-25 10:22 ` Simon Horman
2025-02-13 9:14 ` [PATCH v4 06/14] net-next/yunsilicon: Add pci irq Xin Tian
2025-02-13 9:14 ` [PATCH v4 07/14] net-next/yunsilicon: Init auxiliary device Xin Tian
2025-02-13 14:37 ` Leon Romanovsky
2025-02-14 3:14 ` tianx
2025-02-16 9:59 ` Leon Romanovsky
2025-02-17 2:16 ` tianx
2025-02-13 9:14 ` [PATCH v4 08/14] net-next/yunsilicon: Add ethernet interface Xin Tian
2025-02-13 9:14 ` [PATCH v4 09/14] net-next/yunsilicon: Init net device Xin Tian
2025-02-13 9:14 ` [PATCH v4 10/14] net-next/yunsilicon: Add eth needed qp and cq apis Xin Tian
2025-02-13 9:14 ` [PATCH v4 11/14] net-next/yunsilicon: ndo_open and ndo_stop Xin Tian
2025-02-13 9:14 ` [PATCH v4 12/14] net-next/yunsilicon: Add ndo_start_xmit Xin Tian
2025-02-13 9:14 ` [PATCH v4 13/14] net-next/yunsilicon: Add eth rx Xin Tian
2025-02-13 9:14 ` [PATCH v4 14/14] net-next/yunsilicon: add ndo_get_stats64 Xin Tian
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=20250224185817.GH1615191@kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=masahiroy@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parthiban.veerasooran@microchip.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=tianx@yunsilicon.com \
--cc=wanry@yunsilicon.com \
--cc=weihg@yunsilicon.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;
as well as URLs for NNTP newsgroup(s).