From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, xudu@redhat.com,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
jacob.e.keller@intel.com, intel-wired-lan@lists.osuosl.org,
jmaxwell@redhat.com, magnus.karlsson@intel.com
Subject: Re: [Intel-wired-lan] [PATCH v2 intel-net 0/3] ice: fix Rx data path for heavy 9k MTU traffic
Date: Mon, 20 Jan 2025 15:48:19 +0100 [thread overview]
Message-ID: <Z45iMxA6bBMoLSQ5@boxer> (raw)
In-Reply-To: <20250117132208.1f87a2dc@kernel.org>
On Fri, Jan 17, 2025 at 01:22:08PM -0800, Jakub Kicinski wrote:
> On Fri, 17 Jan 2025 16:18:57 +0100 Maciej Fijalkowski wrote:
> > Subject: [PATCH v2 intel-net 0/3] ice: fix Rx data path for heavy 9k MTU traffic
>
> nit: could you use iwl-net and iwl-next as the tree names?
> That's what we match on in NIPA to categorize Intel patches.
Not sure how I came up with my very own tree target. Will send a v3 then.
WARNING: multiple messages have this Message-ID (diff)
From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<anthony.l.nguyen@intel.com>, <magnus.karlsson@intel.com>,
<jacob.e.keller@intel.com>, <xudu@redhat.com>,
<mschmidt@redhat.com>, <jmaxwell@redhat.com>, <poros@redhat.com>,
<przemyslaw.kitszel@intel.com>
Subject: Re: [PATCH v2 intel-net 0/3] ice: fix Rx data path for heavy 9k MTU traffic
Date: Mon, 20 Jan 2025 15:48:19 +0100 [thread overview]
Message-ID: <Z45iMxA6bBMoLSQ5@boxer> (raw)
In-Reply-To: <20250117132208.1f87a2dc@kernel.org>
On Fri, Jan 17, 2025 at 01:22:08PM -0800, Jakub Kicinski wrote:
> On Fri, 17 Jan 2025 16:18:57 +0100 Maciej Fijalkowski wrote:
> > Subject: [PATCH v2 intel-net 0/3] ice: fix Rx data path for heavy 9k MTU traffic
>
> nit: could you use iwl-net and iwl-next as the tree names?
> That's what we match on in NIPA to categorize Intel patches.
Not sure how I came up with my very own tree target. Will send a v3 then.
next prev parent reply other threads:[~2025-01-20 14:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 15:18 [Intel-wired-lan] [PATCH v2 intel-net 0/3] ice: fix Rx data path for heavy 9k MTU traffic Maciej Fijalkowski
2025-01-17 15:18 ` Maciej Fijalkowski
2025-01-17 15:18 ` [Intel-wired-lan] [PATCH v2 intel-net 1/3] ice: put Rx buffers after being done with current frame Maciej Fijalkowski
2025-01-17 15:18 ` Maciej Fijalkowski
2025-01-17 15:18 ` [Intel-wired-lan] [PATCH v2 intel-net 2/3] ice: gather page_count()'s of each frag right before XDP prog call Maciej Fijalkowski
2025-01-17 15:18 ` Maciej Fijalkowski
2025-01-17 15:19 ` [Intel-wired-lan] [PATCH v2 intel-net 3/3] ice: stop storing XDP verdict within ice_rx_buf Maciej Fijalkowski
2025-01-17 15:19 ` Maciej Fijalkowski
2025-01-17 21:22 ` [Intel-wired-lan] [PATCH v2 intel-net 0/3] ice: fix Rx data path for heavy 9k MTU traffic Jakub Kicinski
2025-01-17 21:22 ` Jakub Kicinski
2025-01-20 14:48 ` Maciej Fijalkowski [this message]
2025-01-20 14:48 ` Maciej Fijalkowski
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=Z45iMxA6bBMoLSQ5@boxer \
--to=maciej.fijalkowski@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=jmaxwell@redhat.com \
--cc=kuba@kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=xudu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.