DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kovacevic, Marko" <marko.kovacevic@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: David Marchand <david.marchand@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 "Mcnamara, John" <john.mcnamara@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: remove file listings
Date: Thu, 17 Jan 2019 16:53:40 +0000	[thread overview]
Message-ID: <6DC05C7C5F25994B81B3F2F214251F660207DD7B@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <6351986.DbtgIHa0yY@xps>

Sorry for not making it clearer,
So if someone was reading it and saw this line

"The examples directory contains sample applications that show how libraries can be used"
 
It would be nice to have a link to the sample applications in the docs like so, which has all the 
Info that was deleted. 

"The examples directory contains :doc:`Sample applications<../sample_app_ug/index>` that show how libraries can be used."


-    examples
-    +-- cmdline            # Example of using the cmdline library
-    +-- exception_path     # Sending packets to and from Linux TAP device
-    +-- helloworld         # Basic Hello World example
-    +-- ip_reassembly      # Example showing IP reassembly
-    +-- ip_fragmentation   # Example showing IPv4 fragmentation
-    +-- ipv4_multicast     # Example showing IPv4 multicast
-    +-- kni                # Kernel NIC Interface (KNI) example
-    +-- l2fwd              # L2 forwarding with and without SR-IOV
-    +-- l3fwd              # L3 forwarding example
-    +-- l3fwd-power        # L3 forwarding example with power management
-    +-- l3fwd-vf           # L3 forwarding example with SR-IOV
-    +-- link_status_interrupt # Link status change interrupt example
-    +-- load_balancer      # Load balancing across multiple cores/sockets
-    +-- multi_process      # Example apps using multiple DPDK processes
-    +-- qos_meter          # QoS metering example
-    +-- qos_sched          # QoS scheduler and dropper example
-    +-- timer              # Example of using librte_timer library
-    +-- vmdq_dcb           # Example of VMDQ and DCB receiving
-    +-- vmdq               # Example of VMDQ receiving
-    +-- vhost              # Example of userspace vhost and switch

Thanks, 
Marko K

  reply	other threads:[~2019-01-17 16:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17  9:05 David Marchand
2019-01-17  9:16 ` Thomas Monjalon
2019-01-17 15:42   ` Kovacevic, Marko
2019-01-17 16:08     ` Thomas Monjalon
2019-01-17 16:53       ` Kovacevic, Marko [this message]
2019-01-17 17:01         ` Thomas Monjalon
2019-01-18  9:29           ` Kovacevic, Marko
2019-01-18  9:33             ` Thomas Monjalon
2019-01-18 10:15               ` David Marchand
2019-01-17 14:36 ` Ferruh Yigit
2019-01-18 15:31 ` [dpdk-dev] [PATCH v2] " David Marchand
2019-01-18 15:35   ` Kovacevic, Marko
2019-01-20 12:10     ` Thomas Monjalon

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=6DC05C7C5F25994B81B3F2F214251F660207DD7B@IRSMSX104.ger.corp.intel.com \
    --to=marko.kovacevic@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=thomas@monjalon.net \
    /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).