DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Cc: "bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 10/10] event/dsw: include DSW event device documentation
Date: Tue, 18 Sep 2018 05:28:57 +0000	[thread overview]
Message-ID: <20180918052848.GA4981@jerin> (raw)
In-Reply-To: <f6ef4683-e09f-81ec-ff05-fca80bb0afee@ericsson.com>

-----Original Message-----
> Date: Mon, 17 Sep 2018 21:17:34 +0200
> From: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> CC: bruce.richardson@intel.com, dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3 10/10] event/dsw: include DSW event
>  device documentation
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
>  Thunderbird/52.9.1
> 
> External Email
> 
> On 2018-09-17 14:29, Jerin Jacob wrote:
> 
> > > diff --git a/doc/guides/eventdevs/dsw.rst b/doc/guides/eventdevs/dsw.rst
> > > new file mode 100644
> > > index 000000000..de41ae9d3
> > > --- /dev/null
> > > +++ b/doc/guides/eventdevs/dsw.rst
> > > @@ -0,0 +1,97 @@
> > > +..  SPDX-License-Identifier: BSD-3-Clause
> > > +    Copyright(c) 2017 Intel Corporation.
> > 
> > Is adding Intel copyright by intention?
> > 
> 
> dsw.rst is a derived work of sw.rst, so I figured I should leave the
> Intel copyright. But maybe that's not needed?

Looks so.

> 
> > > +    Copyright(c) 2018 Ericsson AB
> > > +
> > > +Distributed Software Eventdev Poll Mode Driver
> > > +==============================================
> > > +
> > > +The distributed software eventdev is a parallel implementation of the
> > 
> > s/parallel/driver??
> > 
> 
> I'm not sure I follow. What do you mean?
> 
> "Parallel" here is as in executing on multiple CPU cores.

I read "Parallel" as "alternative" on that context. So I think you can
elaborate a bit, like ending sentence "where scheduler is executing on
multiple CPU cores" or something similar what you like to add more
clarity.

> 
> I could always add "driver".

OK.

> 
> Regards,
>        Mattias

      reply	other threads:[~2018-09-18  5:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  8:02 [dpdk-dev] [PATCH v3 00/10] A Distributed Software Event Device Mattias Rönnblom
2018-09-11  8:02 ` [dpdk-dev] [PATCH v3 01/10] event/dsw: add DSW device registration and build system Mattias Rönnblom
2018-09-17 11:41   ` Jerin Jacob
2018-09-11  8:02 ` [dpdk-dev] [PATCH v3 02/10] event/dsw: add DSW device and queue configuration Mattias Rönnblom
2018-09-11  8:02 ` [dpdk-dev] [PATCH v3 03/10] event/dsw: add DSW port configuration Mattias Rönnblom
2018-09-17 12:12   ` Jerin Jacob
2018-09-11  8:02 ` [dpdk-dev] [PATCH v3 04/10] event/dsw: add support in DSW for linking/unlinking ports Mattias Rönnblom
2018-09-17 12:14   ` Jerin Jacob
2018-09-11  8:02 ` [dpdk-dev] [PATCH v3 05/10] event/dsw: add DSW event scheduling and device start/stop Mattias Rönnblom
2018-09-17 12:22   ` Jerin Jacob
2018-09-11  8:02 ` [dpdk-dev] [PATCH v3 06/10] event/dsw: add DSW port load measurements Mattias Rönnblom
2018-09-11  8:02 ` [dpdk-dev] [PATCH v3 07/10] event/dsw: add load balancing to the DSW event device Mattias Rönnblom
2018-09-11  8:02 ` [dpdk-dev] [PATCH v3 08/10] event/dsw: let DSW event device sort events on dequeue Mattias Rönnblom
2018-09-11  8:02 ` [dpdk-dev] [PATCH v3 09/10] event/dsw: implement eventdev 'xstats' counters in DSW Mattias Rönnblom
2018-09-17 12:23   ` Jerin Jacob
2018-09-11  8:02 ` [dpdk-dev] [PATCH v3 10/10] event/dsw: include DSW event device documentation Mattias Rönnblom
2018-09-17 12:29   ` Jerin Jacob
2018-09-17 19:17     ` Mattias Rönnblom
2018-09-18  5:28       ` Jerin Jacob [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=20180918052848.GA4981@jerin \
    --to=jerin.jacob@caviumnetworks.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mattias.ronnblom@ericsson.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).