From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: dev@dpdk.org, thomas.monjalon@6wind.com
Subject: Re: [dpdk-dev] [PATCH] doc: add EAL bus support in release notes
Date: Tue, 14 Feb 2017 08:53:30 +0530 [thread overview]
Message-ID: <20170214032330.GD3131@localhost.localdomain> (raw)
In-Reply-To: <1486985388-19622-1-git-send-email-shreyansh.jain@nxp.com>
On Mon, Feb 13, 2017 at 04:59:48PM +0530, Shreyansh Jain wrote:
> Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> ---
> doc/guides/rel_notes/release_17_02.rst | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/doc/guides/rel_notes/release_17_02.rst b/doc/guides/rel_notes/release_17_02.rst
> index ec9143c..b5bf0a9 100644
> --- a/doc/guides/rel_notes/release_17_02.rst
> +++ b/doc/guides/rel_notes/release_17_02.rst
> @@ -237,6 +237,16 @@ Resolved Issues
> EAL
> ~~~
>
> +* **Added support for representing buses in EAL**
> +
> + A new structure ``rte_bus`` is introduced in EAL. This allows for devices to
> + be represented by buses they are connected to. A new bus can be added to
> + DPDK by extending the ``rte_bus`` structure and implementing the scan and
> + probe functions. Once a new bus is registered using provided APIs, new
> + devices can be detected and initialized using bus scan and probe callbacks.
> +
> + With this change, devices other than PCI or VDEV type can also be represented
> + in DPDK framework.
>
> Drivers
> ~~~~~~~
Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
next prev parent reply other threads:[~2017-02-14 3:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 11:29 Shreyansh Jain
2017-02-14 0:42 ` Mcnamara, John
2017-02-14 3:23 ` Jerin Jacob [this message]
2017-02-14 12:56 ` Hemant Agrawal
2017-02-14 14:12 ` 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=20170214032330.GD3131@localhost.localdomain \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=shreyansh.jain@nxp.com \
--cc=thomas.monjalon@6wind.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).