All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	Alvaro Karsz <alvaro.karsz@solid-run.com>,
	netdev <netdev@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next v4] net: virtio_net: notifications coalescing support
Date: Wed, 20 Jul 2022 03:05:01 -0400	[thread overview]
Message-ID: <20220720030343-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEvFdMRX-sb7hUpEq+6e04ubehefr8y5Gjnjz8R26f=qDA@mail.gmail.com>

On Wed, Jul 20, 2022 at 03:02:04PM +0800, Jason Wang wrote:
> On Wed, Jul 20, 2022 at 2:45 PM Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > On Tue, Jul 19, 2022 at 05:26:52PM -0700, Jakub Kicinski wrote:
> > > On Mon, 18 Jul 2022 12:11:02 +0300 Alvaro Karsz wrote:
> > > > New VirtIO network feature: VIRTIO_NET_F_NOTF_COAL.
> > > >
> > > > Control a Virtio network device notifications coalescing parameters
> > > > using the control virtqueue.
> > > >
> > > > A device that supports this fetature can receive
> > > > VIRTIO_NET_CTRL_NOTF_COAL control commands.
> > > >
> > > > - VIRTIO_NET_CTRL_NOTF_COAL_TX_SET:
> > > >   Ask the network device to change the following parameters:
> > > >   - tx_usecs: Maximum number of usecs to delay a TX notification.
> > > >   - tx_max_packets: Maximum number of packets to send before a
> > > >     TX notification.
> > > >
> > > > - VIRTIO_NET_CTRL_NOTF_COAL_RX_SET:
> > > >   Ask the network device to change the following parameters:
> > > >   - rx_usecs: Maximum number of usecs to delay a RX notification.
> > > >   - rx_max_packets: Maximum number of packets to receive before a
> > > >     RX notification.
> > > >
> > > > VirtIO spec. patch:
> > > > https://lists.oasis-open.org/archives/virtio-comment/202206/msg00100.html
> > > >
> > > > Signed-off-by: Alvaro Karsz <alvaro.karsz@solid-run.com>
> > >
> > > Waiting a bit longer for Michael's ack, so in case other netdev
> > > maintainer takes this:
> > >
> > > Reviewed-by: Jakub Kicinski <kuba@kernel.org>
> >
> > Yea was going to ack this but looking at the UAPI again we have a
> > problem because we abused tax max frames values 0 and 1 to control napi
> > in the past. technically does not affect legacy cards but userspace
> > can't easily tell the difference, can it?
> 
> The "abuse" only works for iproute2.

That's kernel/userspace API. That's what this patch affects, right?

> For uAPI we know it should follow
> the spec? (anyhow NAPI is something out of the spec)
> 
> Thanks

When you say uAPI here you mean the virtio header. I am not
worried about that just yet (maybe I should be).

> >
> > --
> > MST
> >


  reply	other threads:[~2022-07-20  7:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  9:11 [PATCH net-next v4] net: virtio_net: notifications coalescing support Alvaro Karsz
2022-07-19  7:03 ` Jason Wang
2022-07-19  7:08   ` Alvaro Karsz
2022-07-19  7:12     ` Jason Wang
2022-07-19  7:18       ` Alvaro Karsz
2022-07-19  7:31         ` Jason Wang
2022-07-20  0:26 ` Jakub Kicinski
2022-07-20  6:45   ` Michael S. Tsirkin
2022-07-20  7:02     ` Jason Wang
2022-07-20  7:05       ` Michael S. Tsirkin [this message]
2022-07-20  7:15         ` Jason Wang
2022-07-20  9:05           ` Michael S. Tsirkin
     [not found]         ` <CAJs=3_DHW6qwjjx3ZBH2SVC0kaKviSrHHG+Hsh8-VxAbRNdP7A@mail.gmail.com>
2022-07-20  7:15           ` Michael S. Tsirkin
2022-07-20  7:42             ` Jason Wang
2022-07-20  7:45               ` Jason Wang
2022-07-20  7:56                 ` Alvaro Karsz
2022-07-20  8:28                   ` Jason Wang
2022-07-20  9:09                 ` Michael S. Tsirkin
2022-07-20  6:28 ` Michael S. Tsirkin
2022-07-20  8:52   ` Jason Wang
2022-08-09 19:11 ` Michael S. Tsirkin
2022-08-09 19:14 ` Michael S. Tsirkin
2022-08-29  8:46 ` Xuan Zhuo
2022-08-29  9:14   ` Alvaro Karsz
2022-08-29  9:18     ` Xuan Zhuo

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=20220720030343-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alvaro.karsz@solid-run.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jasowang@redhat.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@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.