Netdev List
 help / color / mirror / Atom feed
From: Heng Qi <hengqi@linux.alibaba.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, virtualization@lists.linux.dev,
	Jason Wang <jasowang@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	"David S. Miller" <davem@davemloft.net>,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [PATCH 0/2] virtio-net: a fix and some updates for virtio dim
Date: Mon, 25 Mar 2024 10:23:55 +0800	[thread overview]
Message-ID: <74e12c42-52d2-4c7f-a9fe-ffe75de603e6@linux.alibaba.com> (raw)
In-Reply-To: <ZfwnSz5vP4KzXNxa@nanopsycho>



在 2024/3/21 下午8:25, Jiri Pirko 写道:
> Thu, Mar 21, 2024 at 12:45:55PM CET, hengqi@linux.alibaba.com wrote:
>> Patch 1 fixes an existing bug. Belongs to the net branch.
> Send separately with "net" indication in the patch brackets:
> https://www.kernel.org/doc/html/next/process/maintainer-netdev.html?highlight=network#tl-dr
>
>
>> Patch 2 attempts to modify the sending of dim cmds to an asynchronous way.
> Not a bugfix, then send separately with "net-next" indication. Net-next
> is currently closed, send it next week.

Will do.

>
>
>> Heng Qi (2):
>>   virtio-net: fix possible dim status unrecoverable
>>   virtio-net: reduce the CPU consumption of dim worker
> The name of the driver is "virtio_net".

'git log --grep="^virtio-net:" --oneline' will see a large number of 
"virtio-net" names.

>
>
>
> pw-bot: cr
>
>
>> drivers/net/virtio_net.c | 273 ++++++++++++++++++++++++++++++++++++++++++-----
>> 1 file changed, 246 insertions(+), 27 deletions(-)
>>
>> -- 
>> 1.8.3.1
>>
>>


      reply	other threads:[~2024-03-25  2:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 11:45 [PATCH 0/2] virtio-net: a fix and some updates for virtio dim Heng Qi
2024-03-21 11:45 ` [PATCH 1/2] virtio-net: fix possible dim status unrecoverable Heng Qi
2024-03-22  5:17   ` Jason Wang
2024-03-25  2:11     ` Heng Qi
2024-03-25  6:29       ` Jason Wang
2024-03-25  6:57         ` Heng Qi
2024-03-25  7:06           ` Jason Wang
2024-03-21 11:45 ` [PATCH 2/2] virtio-net: reduce the CPU consumption of dim worker Heng Qi
2024-03-22  2:03   ` kernel test robot
2024-03-22  5:19   ` Jason Wang
2024-03-25  2:21     ` Heng Qi
2024-03-25  5:57       ` Jason Wang
2024-03-25  7:17         ` Heng Qi
2024-03-25  7:56           ` Jason Wang
2024-03-25  8:22             ` Heng Qi
2024-03-25  8:42               ` Jason Wang
2024-03-26  2:46                 ` Heng Qi
2024-03-26  4:08                   ` Jason Wang
2024-03-26  5:57                     ` Heng Qi
2024-03-26  6:05                       ` Jason Wang
2024-03-22  6:50   ` Dan Carpenter
2024-03-21 12:25 ` [PATCH 0/2] virtio-net: a fix and some updates for virtio dim Jiri Pirko
2024-03-25  2:23   ` Heng Qi [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=74e12c42-52d2-4c7f-a9fe-ffe75de603e6@linux.alibaba.com \
    --to=hengqi@linux.alibaba.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jasowang@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox