From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: brouer@redhat.com, lorenzo@kernel.org, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [PATCH, net-next] net: page_pool: Add documentation on page_pool API
Date: Wed, 12 Feb 2020 08:29:47 +0200 [thread overview]
Message-ID: <20200212062947.GA1171328@apalos.home> (raw)
In-Reply-To: <25360a12-90ce-39ac-4956-8591a8c4eb74@infradead.org>
[...]
>
> what about 'order'? is it optional?
I actually forgot about it, i'll add it on v2
>
> > + * pool_size: size of the ptr_ring
> > + * nid: preferred NUMA node for allocation
> > + * dev: struct device. Used on DMA operations
> > + * dma_dir: DMA direction
> > + * max_len: max DMA sync memory size
> > + * offset: DMA address offset
> > +
> > +* page_pool_put_page(): The outcome of this depends on the page refcnt. If the
> > + driver uses refcnt > 1 this will unmap the page. If the pool object is
> > + responsible for DMA operations and account for the in-flight counting.
>
> Hm, above is not a sentence and it ends with a space character.
> Several lines end with a space character. :(
i'll fix both on V2
>
> > + If the refcnt is 1, the allocator owns the page and will try to recycle and
> > + sync it to be re-used by the device using dma_sync_single_range_for_device().
> > +
> > +* page_pool_release_page(): Unmap the page (if mapped) and account for it on
> > + inflight counters.
>
> inflight is spelled as in-flight earlier. Just choose one way, please.
ok
[...]
> > + page_pool_put_page(page_pool, page, false);
> > + xdp_rxq_info_unreg(&xdp_rxq);
> > + page_pool_destroy(page_pool);
Thanks for the review, i'll wait until net-next reopens and update this
/Ilias
prev parent reply other threads:[~2020-02-12 6:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 15:42 [PATCH, net-next] net: page_pool: Add documentation on page_pool API Ilias Apalodimas
2020-02-11 17:22 ` Randy Dunlap
2020-02-12 6:29 ` Ilias Apalodimas [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=20200212062947.GA1171328@apalos.home \
--to=ilias.apalodimas@linaro.org \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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