DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hiroki Shirokura <slank.dev@gmail.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] L-thread support c++
Date: Tue, 21 Mar 2017 15:53:51 +0000	[thread overview]
Message-ID: <CAHinD4WT6A=zqo_ZTmhYtFghFwTuVd=5r5oKKkCFaCWBoFo=HQ@mail.gmail.com> (raw)
In-Reply-To: <87E6DF08-8CB0-4DF8-9048-21C48D89E8DD@intel.com>

> I believe adding the C++ ifdefs is reasonable. Please send a patch for
the changes.

Thank you for your reply.
So, I'll send a patch soon.

2017年3月22日(水) 0:51 Wiles, Keith <keith.wiles@intel.com>:

>
> > On Mar 21, 2017, at 7:11 AM, Hiroki Shirokura <slank.dev@gmail.com>
> wrote:
> >
> > Hi,
> >
> > This is Hiroki SHIROKURA, japanese student
> > I'm  researching High-Performance-Networking using DPDK
> > and L-thread.
> >
> > L-thread is awesome, but it doesn't support C++.
> > If we want use lthread with C++, we must add only
> > "extern C {}" like a below's commit.
> >
> > https://github.com/susanow/lthread
> >
> https://github.com/susanow/lthread/commit/eb3b8796dfa8ef25dde2340c68b1ca939b4e957b
> >
> > This is very easy but, it wasn't done yet.
> > How do you think about this?
>
> I believe adding the C++ ifdefs is reasonable. Please send a patch for the
> changes.
>
> >
> > Thank you.
> >
> > -----------------------------------------
> > Hiroki SHIROKURA
> >  email: slank.dev@gmail.com
> >  Twitter: @slankdev
> >  Github: slankdev
> >  Facebook: hiroki.shirokura
>
> Regards,
> Keith
>
>

  reply	other threads:[~2017-03-21 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 12:11 Hiroki Shirokura
2017-03-21 15:51 ` Wiles, Keith
2017-03-21 15:53   ` Hiroki Shirokura [this message]
2017-03-21 17:11     ` Hiroki Shirokura

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='CAHinD4WT6A=zqo_ZTmhYtFghFwTuVd=5r5oKKkCFaCWBoFo=HQ@mail.gmail.com' \
    --to=slank.dev@gmail.com \
    --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).