All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: jcfaracco@gmail.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, davem@davemloft.net, jasowang@redhat.com,
	virtualization@lists.linux-foundation.org, dnmendes76@gmail.com
Subject: Re: [PATCH RFC v7 net-next] netdev: pass the stuck queue to the timeout handler
Date: Tue, 3 Dec 2019 10:07:01 -0800	[thread overview]
Message-ID: <20191203100701.0d6a367e@cakuba.netronome.com> (raw)
In-Reply-To: <20191203071101.427592-1-mst@redhat.com>

On Tue, 3 Dec 2019 02:12:48 -0500, Michael S. Tsirkin wrote:
> This allows incrementing the correct timeout statistic without any mess.
> Down the road, devices can learn to reset just the specific queue.
> 
> The patch was generated with the following script:

Still:

Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>

  parent reply	other threads:[~2019-12-03 18:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03  7:12 [PATCH RFC v7 net-next] netdev: pass the stuck queue to the timeout handler Michael S. Tsirkin
2019-12-03  7:32 ` [PATCH RFC v7 net-next 2/1] mlx4: use new txqueue timeout argument Michael S. Tsirkin
2019-12-03  7:32   ` [PATCH RFC v7 net-next 3/1] netronome: use the " Michael S. Tsirkin
2019-12-03 18:09     ` Jakub Kicinski
2019-12-03 18:07 ` Jakub Kicinski [this message]
2019-12-03 18:07 ` [PATCH RFC v7 net-next] netdev: pass the stuck queue to the timeout handler Jakub Kicinski
2019-12-03 19:24 ` Heiner Kallweit
2019-12-03 19:47 ` Shannon Nelson
     [not found] <201912040139.EtA8bCsH%lkp@intel.com>
2019-12-03 18:37 ` Nick Desaulniers
2019-12-03 19:45   ` Michael S. Tsirkin
  -- strict thread matches above, loose matches on Subject: below --
2019-12-03  7:12 Michael S. Tsirkin

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=20191203100701.0d6a367e@cakuba.netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=davem@davemloft.net \
    --cc=dnmendes76@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=jcfaracco@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    /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.