DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v3 0/2] cpu0 and memory channels doc update
Date: Tue, 15 Jul 2025 14:56:27 -0700	[thread overview]
Message-ID: <20250715215718.7388-1-stephen@networkplumber.org> (raw)
In-Reply-To: <20240718184326.21375-1-stephen@networkplumber.org>

This is revised version of earlier patches to address
some guidance about CPU and memory channels in the documentation.

Stephen Hemminger (2):
  doc: add note about CPU 0
  doc: remove use of '-n 4' option in documentation examples

 doc/guides/contributing/documentation.rst     |  2 +-
 doc/guides/cryptodevs/aesni_gcm.rst           |  2 +-
 doc/guides/cryptodevs/aesni_mb.rst            |  2 +-
 doc/guides/cryptodevs/ccp.rst                 |  4 ++--
 doc/guides/cryptodevs/kasumi.rst              |  2 +-
 doc/guides/cryptodevs/null.rst                |  2 +-
 doc/guides/cryptodevs/openssl.rst             |  2 +-
 doc/guides/cryptodevs/snow3g.rst              |  2 +-
 doc/guides/cryptodevs/zuc.rst                 |  2 +-
 doc/guides/howto/lm_bond_virtio_sriov.rst     |  2 +-
 doc/guides/howto/lm_virtio_vhost_user.rst     |  2 +-
 doc/guides/howto/packet_capture_framework.rst |  2 +-
 doc/guides/howto/pvp_reference_benchmark.rst  |  4 ++--
 doc/guides/howto/vfd.rst                      |  4 ++--
 .../virtio_user_for_container_networking.rst  |  4 ++--
 doc/guides/linux_gsg/build_sample_apps.rst    |  5 ++---
 doc/guides/linux_gsg/enable_func.rst          |  5 +++++
 doc/guides/linux_gsg/linux_drivers.rst        |  4 ++--
 doc/guides/nics/build_and_test.rst            |  2 +-
 doc/guides/nics/cpfl.rst                      |  2 +-
 doc/guides/nics/cxgbe.rst                     |  2 +-
 doc/guides/nics/fail_safe.rst                 |  8 ++++----
 doc/guides/nics/hns3.rst                      |  4 ++--
 doc/guides/nics/i40e.rst                      |  6 +++---
 doc/guides/nics/ice.rst                       |  6 +++---
 doc/guides/nics/intel_vf.rst                  |  2 +-
 doc/guides/nics/ipn3ke.rst                    |  4 ++--
 doc/guides/nics/mlx4.rst                      |  2 +-
 doc/guides/nics/mlx5.rst                      |  2 +-
 doc/guides/nics/null.rst                      |  6 +++---
 doc/guides/nics/pcap_ring.rst                 | 18 ++++++++---------
 doc/guides/nics/qede.rst                      |  2 +-
 doc/guides/nics/softnic.rst                   |  2 +-
 doc/guides/nics/thunderx.rst                  |  2 +-
 doc/guides/nics/vhost.rst                     |  2 +-
 doc/guides/nics/virtio.rst                    |  2 +-
 .../link_bonding_poll_mode_drv_lib.rst        | 10 +++++-----
 doc/guides/prog_guide/mempool_lib.rst         |  3 ---
 doc/guides/prog_guide/overview.rst            | 11 +++++-----
 doc/guides/sample_app_ug/cmd_line.rst         |  2 +-
 doc/guides/sample_app_ug/dist_app.rst         |  2 +-
 doc/guides/sample_app_ug/hello_world.rst      |  2 +-
 doc/guides/sample_app_ug/ipsec_secgw.rst      |  4 ++--
 doc/guides/sample_app_ug/ipv4_multicast.rst   |  4 +---
 doc/guides/sample_app_ug/keep_alive.rst       |  2 +-
 doc/guides/sample_app_ug/l2_forward_cat.rst   |  4 ++--
 doc/guides/sample_app_ug/l2_forward_event.rst |  8 ++++----
 .../sample_app_ug/l2_forward_job_stats.rst    |  2 +-
 .../sample_app_ug/l2_forward_real_virtual.rst |  4 ++--
 doc/guides/sample_app_ug/l3_forward.rst       |  8 ++++----
 doc/guides/sample_app_ug/l3_forward_graph.rst |  6 +++---
 doc/guides/sample_app_ug/link_status_intr.rst |  4 ++--
 doc/guides/sample_app_ug/multi_process.rst    | 20 +++++++++----------
 doc/guides/sample_app_ug/ptpclient.rst        |  2 +-
 doc/guides/sample_app_ug/qos_scheduler.rst    |  4 ++--
 doc/guides/sample_app_ug/rxtx_callbacks.rst   |  2 +-
 doc/guides/sample_app_ug/skeleton.rst         |  2 +-
 doc/guides/sample_app_ug/timer.rst            |  2 +-
 doc/guides/sample_app_ug/vdpa.rst             |  2 +-
 doc/guides/sample_app_ug/vhost.rst            |  2 +-
 .../sample_app_ug/vm_power_management.rst     | 12 +++++------
 .../sample_app_ug/vmdq_dcb_forwarding.rst     |  2 +-
 doc/guides/sample_app_ug/vmdq_forwarding.rst  |  2 +-
 doc/guides/testpmd_app_ug/run_app.rst         |  2 +-
 doc/guides/tools/flow-perf.rst                |  2 +-
 65 files changed, 129 insertions(+), 129 deletions(-)

-- 
2.47.2


  parent reply	other threads:[~2025-07-15 21:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18 18:43 [PATCH 1/2] doc: add note about CPU 0 Stephen Hemminger
2024-07-18 18:43 ` [PATCH 2/2] doc: remove use of -n 4 option in documentation Stephen Hemminger
2024-07-19  8:15   ` Bruce Richardson
2024-07-19 13:37   ` Jack Bond-Preston
2024-07-29 19:59 ` [PATCH 1/2] doc: add note about CPU 0 Thomas Monjalon
2024-07-31  4:38 ` [PATCH v2 " Stephen Hemminger
2024-07-31  4:38   ` [PATCH v2 2/2] doc: remove use of -n 4 option in documentation Stephen Hemminger
2024-07-31  8:16     ` Thomas Monjalon
2025-07-15 21:56 ` Stephen Hemminger [this message]
2025-07-15 21:56   ` [PATCH v3 1/2] doc: add note about CPU 0 Stephen Hemminger
2025-07-15 21:56   ` [PATCH v3 2/2] doc: remove use of '-n 4' option in documentation examples Stephen Hemminger
2025-07-15 23:19     ` Stephen Hemminger

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=20250715215718.7388-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    /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).