From: Jakub Kicinski <kuba@kernel.org>
To: Krishna Kumar <krikku@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
tom@herbertland.com, pabeni@redhat.com, horms@kernel.org,
sdf@fomichev.me, kuniyu@google.com, ahmed.zaki@intel.com,
aleksander.lobakin@intel.com, atenart@kernel.org,
jdamato@fastly.com, krishna.ku@flipkart.com
Subject: Re: [PATCH v3 net-next 0/2] net: RPS table overwrite prevention and flow_id caching
Date: Thu, 17 Jul 2025 06:45:54 -0700 [thread overview]
Message-ID: <20250717064554.3e4d9993@kernel.org> (raw)
In-Reply-To: <20250717075659.2725245-1-krikku@gmail.com>
On Thu, 17 Jul 2025 13:26:56 +0530 Krishna Kumar wrote:
> This series splits the previous RPS patch [1] into two patches for
> net-next following reviewer feedback. It also addresses a kernel test
> robot warning by ensuring rps_flow_is_active() is defined only when
> aRFS is enabled. I tested v3 with four builds and reboots: two for
> [PATCH 1/2] with aRFS enabled/disabled, and two for [PATCH 2/2].
Quoting documentation:
Resending after review
~~~~~~~~~~~~~~~~~~~~~~
[...]
The new version of patches should be posted as a separate thread,
not as a reply to the previous posting. Change log should include a link
to the previous posting (see :ref:`Changes requested`).
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#resending-after-review
prev parent reply other threads:[~2025-07-17 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 11:24 [PATCH v2 net-next 0/2] net: RPS table overwrite prevention and flow_id caching Krishna Kumar
2025-07-15 11:24 ` [PATCH v2 net-next 1/2] net: Prevent RPS table overwrite for active flows Krishna Kumar
2025-07-16 4:20 ` kernel test robot
2025-07-15 11:24 ` [PATCH v2 net-next 2/2] net: Cache hash and flow_id to avoid recalculation Krishna Kumar
2025-07-17 7:56 ` [PATCH v3 net-next 0/2] net: RPS table overwrite prevention and flow_id caching Krishna Kumar
2025-07-17 7:56 ` [PATCH v3 net-next 1/2] net: Prevent RPS table overwrite for active flows Krishna Kumar
2025-07-19 0:58 ` Jakub Kicinski
2025-07-20 4:53 ` Krishna Kumar
2025-07-17 7:56 ` [PATCH v3 net-next 2/2] net: Cache hash and flow_id to avoid recalculation Krishna Kumar
2025-07-17 13:45 ` Jakub Kicinski [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=20250717064554.3e4d9993@kernel.org \
--to=kuba@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=krikku@gmail.com \
--cc=krishna.ku@flipkart.com \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=tom@herbertland.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.