From: <wubenqing@ruijie.com.cn>
To: <keith.wiles@intel.com>
Cc: <dev@dpdk.org>
Subject: [dpdk-dev] 回复: Re: Does lthread_cond_wait need a mutex?
Date: Sun, 22 Jul 2018 12:59:15 +0000 [thread overview]
Message-ID: <82A10A71B70FF2449A8AD233969A45A11DB0EF70@FZEX4.ruijie.com.cn> (raw)
In-Reply-To: <8005C6D6-A682-4864-BEBE-8947F16439BF@intel.com>
I'm really looking forward to it :)
________________________________
Regards,
Wubenqing
发件人： Wiles, Keith<mailto:keith.wiles@intel.com>
发送时间： 2018-07-21 21:49
收件人： 吴本卿(研五 福州)<mailto:wubenqing@ruijie.com.cn>
抄送： dev@dpdk.org<mailto:dev@dpdk.org>
主题： Re: [dpdk-dev] Does lthread_cond_wait need a mutex?
> On Jul 20, 2018, at 8:32 PM, wubenqing@ruijie.com.cn wrote:
>
> Hi~
> I would be appreciate it if you could provide your lthread code for me. And I found that DPDK lthreads does not provide lthread_cond_timedwait API which I am looking for.
> Thanks.
I took the lthread code and renamed it and did a number of changes, so it will not be easy to drop into the lthread code as it is not just these functions that have to change. I am very hesitant to give that code out as it is still a work in progress and may not even work correctly in all cases.
I will have a look at the code and see what I can do, but I make no promises.
>
> Regards,
> Wubenqing
>
Regards,
Keith
next prev parent reply other threads:[~2018-07-22 12:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 5:43 [dpdk-dev] " wubenqing
2018-07-18 15:01 ` Wiles, Keith
2018-07-19 2:34 ` wubenqing
2018-07-19 5:21 ` Wiles, Keith
2018-07-21 1:32 ` wubenqing
2018-07-21 13:49 ` Wiles, Keith
2018-07-22 12:59 ` wubenqing [this message]
2018-08-02 7:03 ` [dpdk-dev] 回复: 回复: " wubenqing
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=82A10A71B70FF2449A8AD233969A45A11DB0EF70@FZEX4.ruijie.com.cn \
--to=wubenqing@ruijie.com.cn \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.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).