From: Simon Horman <horms@kernel.org>
To: Sean Anderson <sean.anderson@linux.dev>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Michal Simek <michal.simek@amd.com>,
Heng Qi <hengqi@linux.alibaba.com>
Subject: Re: [PATCH net-next 0/2] net: xilinx: axienet: Enable adaptive IRQ coalescing with DIM
Date: Wed, 4 Sep 2024 17:35:03 +0100 [thread overview]
Message-ID: <20240904163503.GA1722938@kernel.org> (raw)
In-Reply-To: <20240903192524.4158713-1-sean.anderson@linux.dev>
On Tue, Sep 03, 2024 at 03:25:22PM -0400, Sean Anderson wrote:
> To improve performance without sacrificing latency under low load,
> enable DIM. While I appreciate not having to write the library myself, I
> do think there are many unusual aspects to DIM, as detailed in the last
> patch.
>
> This series depends on [1].
>
> [1] https://lore.kernel.org/netdev/20240903180059.4134461-1-sean.anderson@linux.dev/
Hi Sean,
Unfortunately the CI doesn't understand dependencies,
and so it is unable to apply this patchset :(
I would suggest bundling patches for the same driver for net-next
in a single patchset. And in any case, only having one active
at any given time.
--
pw-bot: cr
next prev parent reply other threads:[~2024-09-04 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 19:25 [PATCH net-next 0/2] net: xilinx: axienet: Enable adaptive IRQ coalescing with DIM Sean Anderson
2024-09-03 19:25 ` [PATCH net-next 1/2] net: xilinx: axienet: Support adjusting coalesce settings while running Sean Anderson
2024-09-03 19:25 ` [PATCH net-next 2/2] net: xilinx: axienet: Enable adaptive IRQ coalescing with DIM Sean Anderson
2024-09-04 17:04 ` Eric Dumazet
2024-09-05 14:27 ` Sean Anderson
2024-09-04 16:35 ` Simon Horman [this message]
2024-09-05 14:27 ` [PATCH net-next 0/2] " Sean Anderson
2024-09-06 7:03 ` Simon Horman
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=20240904163503.GA1722938@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hengqi@linux.alibaba.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=sean.anderson@linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).