DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Chautru, Nicolas" <nicolas.chautru@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"gakhil@marvell.com" <gakhil@marvell.com>,
	 "maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
	"Vargas, Hernan" <hernan.vargas@intel.com>
Subject: Re: [PATCH v2 1/2] doc: make the Linux drivers doc more generic
Date: Thu, 09 Mar 2023 19:08:41 +0100	[thread overview]
Message-ID: <2335864.NG923GbCHz@thomas> (raw)
In-Reply-To: <BY5PR11MB445168D202BC1AB154AA23C2F8B59@BY5PR11MB4451.namprd11.prod.outlook.com>

09/03/2023 18:35, Chautru, Nicolas:
> 
> > From: Thomas Monjalon <thomas@monjalon.net>
> > 06/03/2023 18:41, Chautru, Nicolas:
> > > Hi Thomas,
> > >
> > > Any update with regards to that series? Unsure how much more you want it
> > to become generic. Ie. replacing most of "network port" by "PCIe device"
> > 
> > Devices are not always PCI based.
> > The doc should reviewed entirely to make sure it is not restricted to network
> > ports or PCI devices.
> 
> OK not familiar myself with all these other variants, I did not realize you wanted to extend the scope that much. 
> Have you got an ETA for such a doc update?

No ETA, that's why I asked who could help here.


> > > From: Thomas Monjalon <thomas@monjalon.net>
> > > > 15/11/2022 20:59, Nicolas Chautru:
> > > > > Minor change so that for the documentation to be less NIC centric,
> > > > > as these steps can apply more generally to PCIe devices.
> > > > >
> > > > > Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> > > > [...]
> > > > >  Different PMDs may require different kernel drivers in order to
> > > > > work
> > > > properly.
> > > > >  Depending on the PMD being used, a corresponding kernel driver
> > > > > should be loaded, -and network ports should be bound to that driver.
> > > > > +and network ports or other hardware devices should be bound to that
> > driver.
> > > >
> > > > We could completely remove "network ports".
> > > > There are more places in this doc which should be made more generic.
> > > >
> > > > I keep this patch open to remind to work on it.
> > > > Anybody is welcome to improve this patch.




  reply	other threads:[~2023-03-09 18:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 19:59 [PATCH v2 0/2] doc: simplify PMD steps Nicolas Chautru
2022-11-15 19:59 ` [PATCH v2 1/2] doc: make the Linux drivers doc more generic Nicolas Chautru
2022-11-22 14:59   ` Thomas Monjalon
2023-03-06 17:41     ` Chautru, Nicolas
2023-03-06 19:46       ` Thomas Monjalon
2023-03-09 17:35         ` Chautru, Nicolas
2023-03-09 18:08           ` Thomas Monjalon [this message]
2022-11-15 19:59 ` [PATCH v2 2/2] doc: simplify the binding steps Nicolas Chautru
2022-11-22 15:01   ` Thomas Monjalon
2022-11-22 21:21     ` Chautru, Nicolas
2022-11-23  8:35       ` Thomas Monjalon
2022-11-24  1:09         ` Chautru, Nicolas
2022-11-24  8:21           ` 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=2335864.NG923GbCHz@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hernan.vargas@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=nicolas.chautru@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).