public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel•org>
To: Alexander Lobakin <aleksander.lobakin@intel•com>
Cc: "David S. Miller" <davem@davemloft•net>,
	Eric Dumazet <edumazet@google•com>,
	Paolo Abeni <pabeni@redhat•com>,
	Maciej Fijalkowski <maciej.fijalkowski@intel•com>,
	Larysa Zaremba <larysa.zaremba@intel•com>,
	Yunsheng Lin <linyunsheng@huawei•com>,
	Alexander Duyck <alexanderduyck@fb•com>,
	Jesper Dangaard Brouer <hawk@kernel•org>,
	Ilias Apalodimas <ilias.apalodimas@linaro•org>,
	Simon Horman <simon.horman@corigine•com>,
	netdev@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH net-next v4 1/6] page_pool: split types and declarations from page_pool.h
Date: Mon, 7 Aug 2023 13:09:46 -0700	[thread overview]
Message-ID: <20230807130946.22da17b4@kernel.org> (raw)
In-Reply-To: <20230804180529.2483231-2-aleksander.lobakin@intel.com>

On Fri,  4 Aug 2023 20:05:24 +0200 Alexander Lobakin wrote:
> Split types and pure function declarations from page_pool.h
> and add them in page_page/types.h, so that C sources can
> include page_pool.h and headers should generally only include
> page_pool/types.h as suggested by jakub.
> Rename page_pool.h to page_pool/helpers.h to have both in
> one place.

I had to touch this one up a little when merging to fix build 
for the merged-in-meantime mana driver and also update the
patch in Documentation.

  reply	other threads:[~2023-08-07 20:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 18:05 [PATCH net-next v4 0/6] page_pool: a couple of assorted optimizations Alexander Lobakin
2023-08-04 18:05 ` [PATCH net-next v4 1/6] page_pool: split types and declarations from page_pool.h Alexander Lobakin
2023-08-07 20:09   ` Jakub Kicinski [this message]
2023-08-04 18:05 ` [PATCH net-next v4 2/6] net: skbuff: don't include <net/page_pool/types.h> to <linux/skbuff.h> Alexander Lobakin
2023-08-04 18:05 ` [PATCH net-next v4 3/6] page_pool: place frag_* fields in one cacheline Alexander Lobakin
2023-08-04 18:05 ` [PATCH net-next v4 4/6] net: skbuff: avoid accessing page_pool if !napi_safe when returning page Alexander Lobakin
2023-08-04 18:05 ` [PATCH net-next v4 5/6] page_pool: add a lockdep check for recycling in hardirq Alexander Lobakin
2023-08-07 14:48   ` Alexander H Duyck
2023-08-08 13:16     ` Alexander Lobakin
2023-08-08 13:45       ` Alexander Duyck
2023-08-08 13:58         ` Alexander Lobakin
2023-08-08 14:52           ` Alexander Duyck
2023-08-08 15:06             ` Alexander Lobakin
2023-08-08 17:35               ` Alexander Duyck
2023-08-04 18:05 ` [PATCH net-next v4 6/6] net: skbuff: always try to recycle PP pages directly when in softirq Alexander Lobakin
2023-08-07 14:53 ` [PATCH net-next v4 0/6] page_pool: a couple of assorted optimizations Alexander H Duyck
2023-08-07 20:20 ` patchwork-bot+netdevbpf
2023-08-08 13:17   ` Alexander Lobakin

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=20230807130946.22da17b4@kernel.org \
    --to=kuba@kernel$(echo .)org \
    --cc=aleksander.lobakin@intel$(echo .)com \
    --cc=alexanderduyck@fb$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=hawk@kernel$(echo .)org \
    --cc=ilias.apalodimas@linaro$(echo .)org \
    --cc=larysa.zaremba@intel$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linyunsheng@huawei$(echo .)com \
    --cc=maciej.fijalkowski@intel$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=simon.horman@corigine$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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