DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ivan Malov <Ivan.Malov@oktetlabs.ru>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/9] net/sfc: receive prepared packets even in Rx exception case
Date: Thu, 04 Oct 2018 13:04:53 +0300	[thread overview]
Message-ID: <ce4467c4c213571ebfca61bebaad0ed7@oktetlabs.ru> (raw)

On 10/3/2018 12:03 PM, Andrew Rybchenko wrote:
> Make sure that number of prepared packets, completed and added
> Rx ring pointers are reset to zeros on queue purge at stop.
> 
> Fixes: 638bddc99faa ("net/sfc: implement EF10 native Rx datapath")
> Cc: stable at dpdk.org
> 
> Signed-off-by: Andrew Rybchenko <arybchenko at solarflare.com>

Reviewed-by: Ivan Malov <Ivan.Malov@oktetlabs.ru>

             reply	other threads:[~2018-10-04 10:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 10:04 Ivan Malov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-03  9:03 [dpdk-dev] [PATCH 0/9] net/sfc: support more features in EF10 Rx Andrew Rybchenko
2018-10-03  9:03 ` [dpdk-dev] [PATCH 1/9] net/sfc: receive prepared packets even in Rx exception case Andrew Rybchenko

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=ce4467c4c213571ebfca61bebaad0ed7@oktetlabs.ru \
    --to=ivan.malov@oktetlabs.ru \
    --cc=dev@dpdk.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 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).