From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Larysa Zaremba <larysa.zaremba@intel.com>,
netdev@vger.kernel.org, Alexander Duyck <alexanderduyck@fb.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
linux-kernel@vger.kernel.org,
Yunsheng Lin <linyunsheng@huawei.com>,
Michal Kubiak <michal.kubiak@intel.com>,
intel-wired-lan@lists.osuosl.org,
David Christensen <drc@linux.vnet.ibm.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v7 00/12] net: intel: start The Great Code Dedup + Page Pool for iavf
Date: Thu, 14 Dec 2023 11:36:24 +0100 [thread overview]
Message-ID: <2cd811ab-30ac-4f68-b519-00743b64d343@intel.com> (raw)
In-Reply-To: <20231213112835.2262651-1-aleksander.lobakin@intel.com>
From: Alexander Lobakin <aleksander.lobakin@intel.com>
Date: Wed, 13 Dec 2023 12:28:23 +0100
> Here's a two-shot: introduce Intel Ethernet common library (libie) and
> switch iavf to Page Pool. Details are in the commit messages; here's
> a summary:
Now conflicts with bpf-next =\
I'll send a new one soon, hopefully bpf-next will be pulled to net-next
meantime?
Thanks,
Olek
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2023-12-14 10:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 11:28 [Intel-wired-lan] [PATCH net-next v7 00/12] net: intel: start The Great Code Dedup + Page Pool for iavf Alexander Lobakin
2023-12-13 11:28 ` [Intel-wired-lan] [PATCH net-next v7 01/12] page_pool: make sure frag API fields don't span between cachelines Alexander Lobakin
2023-12-13 11:28 ` [Intel-wired-lan] [PATCH net-next v7 02/12] page_pool: don't use driver-set flags field directly Alexander Lobakin
2023-12-13 11:28 ` [Intel-wired-lan] [PATCH net-next v7 03/12] net: intel: introduce Intel Ethernet common library Alexander Lobakin
2023-12-13 11:28 ` [Intel-wired-lan] [PATCH net-next v7 04/12] iavf: kill "legacy-rx" for good Alexander Lobakin
2023-12-13 11:28 ` [Intel-wired-lan] [PATCH net-next v7 05/12] iavf: drop page splitting and recycling Alexander Lobakin
2023-12-13 11:28 ` [Intel-wired-lan] [PATCH net-next v7 06/12] page_pool: constify some read-only function arguments Alexander Lobakin
2023-12-13 11:28 ` [Intel-wired-lan] [PATCH net-next v7 07/12] page_pool: add DMA-sync-for-CPU inline helper Alexander Lobakin
2023-12-13 11:28 ` [Intel-wired-lan] [PATCH net-next v7 08/12] libie: add Rx buffer management (via Page Pool) Alexander Lobakin
2023-12-13 11:28 ` [Intel-wired-lan] [PATCH net-next v7 09/12] iavf: pack iavf_ring more efficiently Alexander Lobakin
2023-12-13 11:28 ` [Intel-wired-lan] [PATCH net-next v7 10/12] iavf: switch to Page Pool Alexander Lobakin
2023-12-13 11:28 ` [Intel-wired-lan] [PATCH net-next v7 11/12] libie: add common queue stats Alexander Lobakin
2023-12-13 11:28 ` [Intel-wired-lan] [PATCH net-next v7 12/12] iavf: switch queue stats to libie Alexander Lobakin
2023-12-14 10:36 ` Alexander Lobakin [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=2cd811ab-30ac-4f68-b519-00743b64d343@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=alexanderduyck@fb.com \
--cc=davem@davemloft.net \
--cc=drc@linux.vnet.ibm.com \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=larysa.zaremba@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linyunsheng@huawei.com \
--cc=maciej.fijalkowski@intel.com \
--cc=michal.kubiak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
/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