From: Matej Vido <vido@cesnet.cz>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 3/5] net/szedata2: refactor ibuf and obuf address definition
Date: Wed, 31 May 2017 10:33:35 +0200 [thread overview]
Message-ID: <88fb0928-3b53-8660-0d8b-36a27218abe6@cesnet.cz> (raw)
In-Reply-To: <c6b87fbb-5abf-b0a8-944f-3734df45b8c6@intel.com>
On 29.05.2017 14:41, Ferruh Yigit wrote:
> On 5/26/2017 7:05 PM, Matej Vido wrote:
>> This is to prepare for firmwares with multiple ibufs and obufs.
>> Offsets of ibufs and obufs are defined in array.
> I was thinking ibufs and obufs as queues, but since link functions
> updated per ibufs it looks like ports, can you please provide some
> information what is ibufs and obufs?
>
> What is the benefit of having multiple ibufs and obufs?
Hi Ferruh,
ibufs and obufs are the modules in FPGA firmware implementing the
Ethernet port (MAC layer, to be exact). There is one ibuf+obuf per
Ethernet port. Our cards and firmwares allow one 100GE physical port to
be one Ethernet port, or split into 10 ports of 10GE. However, all DMA
queues in the device are shared between all Ethernet ports. Packet from
any port can be passed by crossbar logic to any DMA queue (and from any
DMA queue to any port).
Regards,
Matej
>
>> Functions which operate on ibufs and obufs iterate over this array.
>>
>> Signed-off-by: Matej Vido <vido@cesnet.cz>
> <...>
next prev parent reply other threads:[~2017-05-31 8:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 18:05 [dpdk-dev] [PATCH 1/5] net/szedata2: refactor ibuf and obuf names Matej Vido
2017-05-26 18:05 ` [dpdk-dev] [PATCH 2/5] net/szedata2: refactor ibuf and obuf read and write Matej Vido
2017-05-26 18:05 ` [dpdk-dev] [PATCH 3/5] net/szedata2: refactor ibuf and obuf address definition Matej Vido
2017-05-29 12:41 ` Ferruh Yigit
2017-05-31 8:33 ` Matej Vido [this message]
2017-05-31 9:12 ` Ferruh Yigit
2017-05-26 18:05 ` [dpdk-dev] [PATCH 4/5] net/szedata2: move ibuf and obuf to specific header Matej Vido
2017-05-26 18:05 ` [dpdk-dev] [PATCH 5/5] net/szedata2: add more supported firmwares Matej Vido
2017-05-29 12:42 ` Ferruh Yigit
2017-05-31 8:34 ` Matej Vido
2017-05-31 9:11 ` Ferruh Yigit
2017-05-29 12:40 ` [dpdk-dev] [PATCH 1/5] net/szedata2: refactor ibuf and obuf names Ferruh Yigit
2017-05-31 8:32 ` Matej Vido
2017-06-12 12:03 ` [dpdk-dev] [PATCH v2 " Matej Vido
2017-06-12 12:03 ` [dpdk-dev] [PATCH v2 2/5] net/szedata2: refactor ibuf and obuf read and write Matej Vido
2017-06-12 12:03 ` [dpdk-dev] [PATCH v2 3/5] net/szedata2: refactor ibuf and obuf address definition Matej Vido
2017-06-12 12:03 ` [dpdk-dev] [PATCH v2 4/5] net/szedata2: move ibuf and obuf to specific header Matej Vido
2017-06-12 12:03 ` [dpdk-dev] [PATCH v2 5/5] net/szedata2: add more supported firmwares Matej Vido
2017-06-12 14:35 ` [dpdk-dev] [PATCH v2 1/5] net/szedata2: refactor ibuf and obuf names Ferruh Yigit
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=88fb0928-3b53-8660-0d8b-36a27218abe6@cesnet.cz \
--to=vido@cesnet.cz \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).