From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] doc/guides/nics: split pcap_ring into separate documentation files
Date: Mon, 9 Feb 2026 16:05:21 -0800 [thread overview]
Message-ID: <20260209160521.50c66fa3@phoenix.local> (raw)
In-Reply-To: <20260108202441.173351-1-stephen@networkplumber.org>
On Thu, 8 Jan 2026 12:24:41 -0800
Stephen Hemminger <stephen@networkplumber.org> wrote:
> The documentation had combined to unrelated drivers together.
> Use AI to split into two separate files:
> pcap.rst for the pcap PMD and ring.rst for the ring PMD.
>
> Changes to pcap.rst:
> - Use "pcap" consistently instead of mixed "libpcap/pcap/PCAP" naming
> - Remove Linux-specific references; document support for Linux, FreeBSD,
> and Windows
> - Add reference to upstream libpcap documentation
> - Add multi-queue support section explaining queue count determination
> and file handle limitations
> - Use ``--vdev=net_pcap0`` format consistently
> - Remove deprecated rte_eth_from_pcaps() API section
> - Improve technical documentation style throughout
>
> Changes to ring.rst:
> - Use ``--vdev=net_ring0`` format consistently
> - Fix inconsistent "Rings-based/Ring-based" naming
> - Retain rte_eth_from_rings() API section with usage examples
> - Improve technical documentation style throughout
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Queued to next-net
prev parent reply other threads:[~2026-02-10 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 20:24 [PATCH] doc/guides/nics: split pcap_ring into separate documentation files Stephen Hemminger
2026-02-10 0:05 ` Stephen Hemminger [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=20260209160521.50c66fa3@phoenix.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.