From: x-fn-spp@sl.ntt-tx.co.jp
To: ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Cc: spp@dpdk.org
Subject: [spp] [PATCH 0/3] Fix slow response of command in spp_vf and spp_mirror
Date: Fri, 11 Jan 2019 13:27:40 +0900 [thread overview]
Message-ID: <201901110427.x0B4Rh3x023480@imss03.silk.ntt-tx.co.jp> (raw)
From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
This series of patches is to fix slow response of spp_vf and spp_mirror.
It is because sleep(1) after accepting command is too long.
To fix the problem, it is replaced with usleep(100) for making a response
in a reasonable short time.
Hideyuki Yamashita (3):
spp_vf: add sleep after disconnect detection
spp_vf: improve command response time
spp_mirror: improve command response time
src/mirror/spp_mirror.c | 7 +++++--
src/vf/common/command_proc.c | 8 +++++---
src/vf/spp_vf.c | 7 ++++++-
3 files changed, 16 insertions(+), 6 deletions(-)
--
2.17.1
reply other threads:[~2019-01-11 4:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201901110427.x0B4Rh3x023480@imss03.silk.ntt-tx.co.jp \
--to=x-fn-spp@sl.ntt-tx.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--cc=spp@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).