dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: xiangxia.m.yue@gmail.com, jianfeng.tan@intel.com
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 1/2] vhost: make sure vhost fdset-thread created successfully
Date: Fri, 30 Mar 2018 10:03:52 +0200	[thread overview]
Message-ID: <eaf70f4b-4ec8-2e39-4f34-15d30e8ecb67@redhat.com> (raw)
In-Reply-To: <1521771531-95836-1-git-send-email-xiangxia.m.yue@gmail.com>



On 03/23/2018 03:18 AM, xiangxia.m.yue@gmail.com wrote:
> From: Tonghao Zhang <xiangxia.m.yue@gmail.com>
> 
> When first call the 'rte_vhost_driver_start', the
> fdset_event_dispatch thread should be created successfully.
> Because the vhost uses it to poll socket events for vhost
> server or clients. Without it, for example, vhost will not
> get the connection event.
> 
> This patch returns err code directly when created not successful.
> 
> Signed-off-by: Tonghao Zhang <xiangxia.m.yue@gmail.com>
> Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>
> ---
> v2:
> According to rte_vhost_driver_start doc, replace the err code
> of pthread_create with -1.
> ---
>   lib/librte_vhost/socket.c | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)

Applied to dpdk-next-virtio/master.

Thanks,
Maxime

      parent reply	other threads:[~2018-03-30  8:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23  2:18 [PATCH v2 1/2] vhost: make sure vhost fdset-thread created successfully xiangxia.m.yue
2018-03-23  2:18 ` [PATCH v2 2/2] vhost: add fdset-event thread name xiangxia.m.yue
2018-03-30  8:05   ` Maxime Coquelin
2018-03-30  8:03 ` Maxime Coquelin [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=eaf70f4b-4ec8-2e39-4f34-15d30e8ecb67@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.com \
    --cc=xiangxia.m.yue@gmail.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;
as well as URLs for NNTP newsgroup(s).