From: Jakub Kicinski <kuba@kernel•org>
To: Heng Qi <hengqi@linux•alibaba.com>
Cc: netdev@vger•kernel.org,
virtualization@lists•linux-foundation.org,
Jason Wang <jasowang@redhat•com>,
"Michael S . Tsirkin" <mst@redhat•com>,
Eric Dumazet <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>,
"David S . Miller" <davem@davemloft•net>,
Jesper Dangaard Brouer <hawk@kernel•org>,
John Fastabend <john.fastabend@gmail•com>,
Alexei Starovoitov <ast@kernel•org>,
Simon Horman <horms@kernel•org>,
xuanzhuo@linux•alibaba.com
Subject: Re: [PATCH net-next v3 5/5] virtio-net: return -EOPNOTSUPP for adaptive-tx
Date: Tue, 14 Nov 2023 23:23:05 -0500 [thread overview]
Message-ID: <20231114232305.4cd58415@kernel.org> (raw)
In-Reply-To: <6a79229fbeb72edf41185a45a0f9ea5cd87a1086.1699938946.git.hengqi@linux.alibaba.com>
On Tue, 14 Nov 2023 13:55:47 +0800 Heng Qi wrote:
> We do not currently support tx dim, so respond to -EOPNOTSUPP.
Hm, why do you need this? You don't set ADAPTIVE_TX in
.supported_coalesce_params, so core should prevent attempts
to enable ADAPTIVE_TX.
next prev parent reply other threads:[~2023-11-15 4:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 5:55 [PATCH net-next v3 0/5] virtio-net: support dynamic coalescing moderation Heng Qi
2023-11-14 5:55 ` [PATCH net-next v3 1/5] virtio-net: returns whether napi is complete Heng Qi
2023-11-14 5:55 ` [PATCH net-next v3 2/5] virtio-net: separate rx/tx coalescing moderation cmds Heng Qi
2023-11-14 5:55 ` [PATCH net-next v3 3/5] virtio-net: extract virtqueue coalescig cmd for reuse Heng Qi
2023-11-14 5:55 ` [PATCH net-next v3 4/5] virtio-net: support rx netdim Heng Qi
2023-11-14 5:55 ` [PATCH net-next v3 5/5] virtio-net: return -EOPNOTSUPP for adaptive-tx Heng Qi
2023-11-15 4:23 ` Jakub Kicinski [this message]
2023-11-15 4:52 ` Heng Qi
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=20231114232305.4cd58415@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=hengqi@linux$(echo .)alibaba.com \
--cc=horms@kernel$(echo .)org \
--cc=jasowang@redhat$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=mst@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=virtualization@lists$(echo .)linux-foundation.org \
--cc=xuanzhuo@linux$(echo .)alibaba.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