All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Xie, Huawei" <huawei.xie@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH 5/5] virtio: optimize transmit enqueue
Date: Tue, 20 Oct 2015 01:48:41 +0000	[thread overview]
Message-ID: <C37D651A908B024F974696C65296B57B4B12E0AD@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: 1445231772-17467-6-git-send-email-stephen@networkplumber.org

On 10/19/2015 1:16 PM, Stephen Hemminger wrote:
> All the error checks in virtqueue_enqueue_xmit are already done
> by the caller. Therefore they can be removed to improve performance.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Exactly the same thought as i commented in previous patch. We should
remove unnecessary checks as caller ensures they will pass.
We need check whether we need recheck "need" again after
virtio_xmit_cleanup for the previous indirect patch.
 
Acked-by: Huawei Xie <huawei.xie@intel.com>
> ---
>  drivers/net/virtio/virtio_rxtx.c | 23 ++---------------------
>  1 file changed, 2 insertions(+), 21 deletions(-)
>
>


  reply	other threads:[~2015-10-20  1:49 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19  5:16 [PATCH v2 0/5] virtio: Tx performance improvements Stephen Hemminger
2015-10-19  5:16 ` [PATCH 1/5] virtio: clean up space checks on xmit Stephen Hemminger
2015-10-19  8:02   ` Xie, Huawei
2015-10-19 15:48     ` Stephen Hemminger
2015-10-19 16:27       ` Xie, Huawei
2015-10-19  5:16 ` [PATCH 2/5] virtio: don't use unlikely for normal tx stuff Stephen Hemminger
2015-10-19  5:16 ` [PATCH 3/5] virtio: use indirect ring elements Stephen Hemminger
2015-10-19 13:19   ` Xie, Huawei
2015-10-19 15:47     ` Stephen Hemminger
2015-10-19 16:18       ` Xie, Huawei
2015-10-30 18:01   ` Thomas Monjalon
2015-10-19  5:16 ` [PATCH 4/5] virtio: use any layout on transmit Stephen Hemminger
2015-10-19 16:28   ` Xie, Huawei
2015-10-19 16:43     ` Stephen Hemminger
2015-10-19 16:56       ` Xie, Huawei
2015-10-26 23:47         ` Stephen Hemminger
2015-10-19 17:19     ` Stephen Hemminger
2015-10-19  5:16 ` [PATCH 5/5] virtio: optimize transmit enqueue Stephen Hemminger
2015-10-20  1:48   ` Xie, Huawei [this message]
2015-10-21 13:18 ` [PATCH v2 0/5] virtio: Tx performance improvements Thomas Monjalon
2015-10-22 10:38   ` Xie, Huawei
2015-10-22 12:13     ` Xie, Huawei
2015-10-22 16:04     ` Stephen Hemminger
2015-10-23  9:00       ` Xie, Huawei
2015-10-26 23:52         ` Stephen Hemminger
2015-10-27  1:56           ` Xie, Huawei
2015-10-27  2:23             ` Stephen Hemminger
2015-10-27  2:38               ` Xie, Huawei
2015-10-26 14:05 ` Xie, Huawei
2016-01-05  8:10   ` Xie, Huawei
2016-01-06 12:03     ` Thomas Monjalon
2016-01-14 13:49       ` Xie, Huawei
2016-03-04  6:18         ` Xie, Huawei
2016-03-04 18:17           ` Stephen Hemminger
2016-03-08  1:38             ` Xie, Huawei

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=C37D651A908B024F974696C65296B57B4B12E0AD@SHSMSX101.ccr.corp.intel.com \
    --to=huawei.xie@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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.