From: Ivan Boule <ivan.boule@6wind.com>
To: David Marchand <david.marchand@6wind.com>, dev@dpdk.org
Cc: viktorin@rehivetech.com
Subject: Re: [PATCH v2 9/9] pci: implement automatic bind/unbind
Date: Wed, 3 Feb 2016 10:26:26 +0100 [thread overview]
Message-ID: <56B1C7C2.6070402@6wind.com> (raw)
In-Reply-To: <1454078953-23744-10-git-send-email-david.marchand@6wind.com>
On 01/29/2016 03:49 PM, David Marchand wrote:
> Reuse pci hook to implement automatic bind / unbind.
> The more I look at this, the more I think this should go to the PMDs
> themselves (with options per devices to control this), with EAL offering
> helpers to achieve this.
This sounds good to me.
As a basic software design rule, the decisions of using a given resource
and/or performing a given operation (the intelligent knowledge) should
systematically be taken at the maximum possible software level.
Conversely, such high-level decisions should be offered the most
appropriate low-level services to facilitate their implementation.
In the case we are considering here - the need to bind a PCI device -
the Poll Mode Driver of that device is the only component which actually
knows.
Conversely, the EAL layer is the best place where to implement the
OS-dependent and/or architecture-dependent device binding services to be
invoked by PMDs at PCI device probing time.
My 2 cents,
Ivan
--
Ivan Boule
6WIND Development Engineer
next prev parent reply other threads:[~2016-02-03 9:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 15:27 [PATCH 0/9] pci cleanup and blacklist rework David Marchand
2016-01-22 15:27 ` [PATCH 1/9] pci: no need for dynamic tailq init David Marchand
2016-01-22 15:27 ` [PATCH 2/9] pci: add internal device list helpers David Marchand
2016-01-22 15:27 ` [PATCH 3/9] pci: minor cleanup David Marchand
2016-01-22 15:27 ` [PATCH 4/9] pci: rework sysfs parsing for driver David Marchand
2016-01-22 15:27 ` [PATCH 5/9] pci: factorize probe/detach code David Marchand
2016-01-22 15:27 ` [PATCH 6/9] pci: cosmetic change David Marchand
2016-01-22 15:27 ` [PATCH 7/9] pci: factorize driver search David Marchand
2016-01-22 15:27 ` [PATCH 8/9] pci: remove driver lookup from detach David Marchand
2016-01-22 15:27 ` [PATCH 9/9] pci: blacklist only in global probe function David Marchand
2016-01-27 13:07 ` [PATCH 0/9] pci cleanup and blacklist rework David Marchand
2016-01-29 14:49 ` [PATCH v2 " David Marchand
2016-01-29 14:49 ` [PATCH v2 1/9] pci: add internal device list helpers David Marchand
2016-01-29 14:49 ` [PATCH v2 2/9] pci/linux: minor cleanup David Marchand
2016-01-29 14:49 ` [PATCH v2 3/9] pci/linux: rework sysfs parsing for driver David Marchand
2016-01-29 14:49 ` [PATCH v2 4/9] pci: factorize probe/detach code David Marchand
2016-01-29 14:49 ` [PATCH v2 5/9] pci: cosmetic change David Marchand
2016-01-29 14:49 ` [PATCH v2 6/9] pci: factorize driver search David Marchand
2016-01-29 14:49 ` [PATCH v2 7/9] pci: remove driver lookup from detach David Marchand
2016-01-29 14:49 ` [PATCH v2 8/9] pci: implement blacklist using a hook David Marchand
2016-01-29 14:49 ` [PATCH v2 9/9] pci: implement automatic bind/unbind David Marchand
2016-02-03 9:26 ` Ivan Boule [this message]
2016-02-08 13:31 ` [PATCH v2 0/9] pci cleanup and blacklist rework Jan Viktorin
2016-02-09 8:39 ` David Marchand
2016-03-16 16:07 ` Jan Viktorin
2016-03-22 10:24 ` David Marchand
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=56B1C7C2.6070402@6wind.com \
--to=ivan.boule@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=viktorin@rehivetech.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 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.