Performance of access in a fixed-size array is very good
because of cache locality
and because there is a single pointer to dereference.
The only drawback is the lack of flexibility:
the size of such an array cannot be increase at runtime.
An approach to this problem is to allocate the array at ru
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, 14 June 2021 12.59
>
> Performance of access in a fixed-size array is very good
> because of cache locality
> and because there is a single pointer to dereference.
> The only drawback is the lack of flexibility:
On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> > Sent: Monday, 14 June 2021 12.59
> >
> > Performance of access in a fixed-size array is very good
> > because of cache locality
> > and because there is a sin
14/06/2021 14:22, Morten Brørup:
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> > Sent: Monday, 14 June 2021 12.59
> >
> > Performance of access in a fixed-size array is very good
> > because of cache locality
> > and because there is a single pointer to dereference.
>
14/06/2021 15:15, Bruce Richardson:
> On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> > > Sent: Monday, 14 June 2021 12.59
> > >
> > > Performance of access in a fixed-size array is very good
> > > because
>
> 14/06/2021 15:15, Bruce Richardson:
> > On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> > > > Sent: Monday, 14 June 2021 12.59
> > > >
> > > > Performance of access in a fixed-size array is very goo
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, 14 June 2021 15.32
>
> 14/06/2021 15:15, Bruce Richardson:
> > On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas
> Monjalon
> > >
On Mon, Jun 14, 2021 at 8:29 PM Ananyev, Konstantin
wrote:
>
>
> >
> > 14/06/2021 15:15, Bruce Richardson:
> > > On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> > > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> > > > > Sent: Monday, 14 June 2021 12.59
> >
> > 14/06/2021 15:15, Bruce Richardson:
> > > On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> > > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> > > > > Sent: Monday, 14 June 2021 12.59
> > > > >
> > > > > Performance of access in a fixed-size arr
14/06/2021 17:48, Morten Brørup:
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> It would be much simpler to just increase RTE_MAX_ETHPORTS to something big
> enough to hold a sufficiently large array. And possibly add an
> rte_max_ethports variable to indicate the numb
14/06/2021 17:48, Jerin Jacob:
> On Mon, Jun 14, 2021 at 8:29 PM Ananyev, Konstantin
> wrote:
> > > 14/06/2021 15:15, Bruce Richardson:
> > > > On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> > > > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> > > > >
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Tuesday, 15 June 2021 08.48
>
> 14/06/2021 17:48, Morten Brørup:
> > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas
> Monjalon
> > It would be much simpler to just increase RTE_MAX_ETHPORTS to
> something
On Tue, Jun 15, 2021 at 12:22 PM Thomas Monjalon wrote:
>
> 14/06/2021 17:48, Jerin Jacob:
> > On Mon, Jun 14, 2021 at 8:29 PM Ananyev, Konstantin
> > wrote:
> > > > 14/06/2021 15:15, Bruce Richardson:
> > > > > On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> > > > > > > From: de
On Tue, Jun 15, 2021 at 09:53:33AM +0200, Morten Brørup wrote:
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> > Sent: Tuesday, 15 June 2021 08.48
> >
> > 14/06/2021 17:48, Morten Brørup:
> > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas
> > Monjalon
>
15/06/2021 10:00, Jerin Jacob:
> On Tue, Jun 15, 2021 at 12:22 PM Thomas Monjalon wrote:
> > 14/06/2021 17:48, Jerin Jacob:
> > > On Mon, Jun 14, 2021 at 8:29 PM Ananyev, Konstantin
> > > wrote:
> > > > > 14/06/2021 15:15, Bruce Richardson:
> > > > > > While I dislike the hard-coded limits in DPD
15/06/2021 10:44, Bruce Richardson:
> On Tue, Jun 15, 2021 at 09:53:33AM +0200, Morten Brørup wrote:
> > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> > > Sent: Tuesday, 15 June 2021 08.48
> > >
> > > 14/06/2021 17:48, Morten Brørup:
> > > > > From: dev [mailto:dev-boun.
> 14/06/2021 17:48, Jerin Jacob:
> > On Mon, Jun 14, 2021 at 8:29 PM Ananyev, Konstantin
> > wrote:
> > > > 14/06/2021 15:15, Bruce Richardson:
> > > > > On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> > > > > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas
> >
15/06/2021 11:33, Ananyev, Konstantin:
> > 14/06/2021 17:48, Jerin Jacob:
> > > On Mon, Jun 14, 2021 at 8:29 PM Ananyev, Konstantin
> > > wrote:
> > > > I had only a quick look at your approach so far.
> > > > But from what I can read, in MT environment your suggestion will require
> > > > extra s
>
> 15/06/2021 11:33, Ananyev, Konstantin:
> > > 14/06/2021 17:48, Jerin Jacob:
> > > > On Mon, Jun 14, 2021 at 8:29 PM Ananyev, Konstantin
> > > > wrote:
> > > > > I had only a quick look at your approach so far.
> > > > > But from what I can read, in MT environment your suggestion will
> > >
15/06/2021 12:08, Ananyev, Konstantin:
> > 15/06/2021 11:33, Ananyev, Konstantin:
> > > > 14/06/2021 17:48, Jerin Jacob:
> > > > > On Mon, Jun 14, 2021 at 8:29 PM Ananyev, Konstantin
> > > > > wrote:
> > > > > > I had only a quick look at your approach so far.
> > > > > > But from what I can read,
>
> 15/06/2021 12:08, Ananyev, Konstantin:
> > > 15/06/2021 11:33, Ananyev, Konstantin:
> > > > > 14/06/2021 17:48, Jerin Jacob:
> > > > > > On Mon, Jun 14, 2021 at 8:29 PM Ananyev, Konstantin
> > > > > > wrote:
> > > > > > > I had only a quick look at your approach so far.
> > > > > > > But fr
On Tue, Jun 15, 2021 at 12:18 PM Thomas Monjalon wrote:
>
> 14/06/2021 17:48, Morten Brørup:
> > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> > It would be much simpler to just increase RTE_MAX_ETHPORTS to something big
> > enough to hold a sufficiently large array. An
On 14-Jun-21 11:58 AM, Thomas Monjalon wrote:
Performance of access in a fixed-size array is very good
because of cache locality
and because there is a single pointer to dereference.
The only drawback is the lack of flexibility:
the size of such an array cannot be increase at runtime.
An approac
> From: Jerin Jacob [mailto:jerinjac...@gmail.com]
> Sent: Wednesday, 16 June 2021 11.42
>
> On Tue, Jun 15, 2021 at 12:18 PM Thomas Monjalon
> wrote:
> >
> > 14/06/2021 17:48, Morten Brørup:
> > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas
> Monjalon
> > > It would be much sim
On Wed, Jun 16, 2021 at 4:57 PM Morten Brørup
wrote:
>
> > From: Jerin Jacob [mailto:jerinjac...@gmail.com]
> > Sent: Wednesday, 16 June 2021 11.42
> >
> > On Tue, Jun 15, 2021 at 12:18 PM Thomas Monjalon
> > wrote:
> > >
> > > 14/06/2021 17:48, Morten Brørup:
> > > > > From: dev [mailto:dev-bou
On 16-Jun-21 10:42 AM, Jerin Jacob wrote:
On Tue, Jun 15, 2021 at 12:18 PM Thomas Monjalon wrote:
14/06/2021 17:48, Morten Brørup:
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
It would be much simpler to just increase RTE_MAX_ETHPORTS to something big
enough to hold
On Wed, Jun 16, 2021 at 5:52 PM Burakov, Anatoly
wrote:
>
> On 16-Jun-21 10:42 AM, Jerin Jacob wrote:
> > On Tue, Jun 15, 2021 at 12:18 PM Thomas Monjalon
> > wrote:
> >>
> >> 14/06/2021 17:48, Morten Brørup:
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> >>> It wo
On Wed, Jun 16, 2021 at 01:27:17PM +0200, Morten Brørup wrote:
> > From: Jerin Jacob [mailto:jerinjac...@gmail.com]
> > Sent: Wednesday, 16 June 2021 11.42
> >
> > On Tue, Jun 15, 2021 at 12:18 PM Thomas Monjalon
> > wrote:
> > >
> > > 14/06/2021 17:48, Morten Brørup:
> > > > > From: dev [mailto:
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Bruce Richardson
> Sent: Wednesday, 16 June 2021 15.03
>
> On Wed, Jun 16, 2021 at 01:27:17PM +0200, Morten Brørup wrote:
> > > From: Jerin Jacob [mailto:jerinjac...@gmail.com]
> > > Sent: Wednesday, 16 June 2021 11.42
> > >
> > > On Tue, Jun
On Wed, Jun 16, 2021 at 05:01:46PM +0200, Morten Brørup wrote:
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Bruce Richardson
> > Sent: Wednesday, 16 June 2021 15.03
> >
> > On Wed, Jun 16, 2021 at 01:27:17PM +0200, Morten Brørup wrote:
> > > > From: Jerin Jacob [mailto:jerinjac...@gmai
2021-06-16 18:29 (UTC+0530), Jerin Jacob:
> On Wed, Jun 16, 2021 at 5:52 PM Burakov, Anatoly
> wrote:
> >
> > On 16-Jun-21 10:42 AM, Jerin Jacob wrote:
> > > On Tue, Jun 15, 2021 at 12:18 PM Thomas Monjalon
> > > wrote:
> > >>
> > >> 14/06/2021 17:48, Morten Brørup:
> > From: dev [mai
On 6/14/2021 4:54 PM, Ananyev, Konstantin wrote:
>
>
>>>
>>> 14/06/2021 15:15, Bruce Richardson:
On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
>> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
>> Sent: Monday, 14 June 2021 12.59
>>
>> Pe
> >>>
> >>> 14/06/2021 15:15, Bruce Richardson:
> On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> >> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> >> Sent: Monday, 14 June 2021 12.59
> >>
> >> Performance of access in a fixed-size arr
> From: Ananyev, Konstantin [mailto:konstantin.anan...@intel.com]
> Sent: Thursday, 17 June 2021 16.59
>
> > >>>
> > >>> 14/06/2021 15:15, Bruce Richardson:
> > On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> > >> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thoma
On 6/17/2021 3:58 PM, Ananyev, Konstantin wrote:
>
>
>
> 14/06/2021 15:15, Bruce Richardson:
>> On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
Sent: Monday, 14 June 2021 12.59
>>
On 6/17/2021 4:17 PM, Morten Brørup wrote:
>> From: Ananyev, Konstantin [mailto:konstantin.anan...@intel.com]
>> Sent: Thursday, 17 June 2021 16.59
>>
>>
>> 14/06/2021 15:15, Bruce Richardson:
>>> On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> From: dev [mailto
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ferruh Yigit
> Sent: Thursday, 17 June 2021 18.13
>
> On 6/17/2021 4:17 PM, Morten Brørup wrote:
> >> From: Ananyev, Konstantin [mailto:konstantin.anan...@intel.com]
> >> Sent: Thursday, 17 June 2021 16.59
> >>
> >>
> >> 14/06/2021 15:
> On 6/17/2021 4:17 PM, Morten Brørup wrote:
> >> From: Ananyev, Konstantin [mailto:konstantin.anan...@intel.com]
> >> Sent: Thursday, 17 June 2021 16.59
> >>
> >>
> >> 14/06/2021 15:15, Bruce Richardson:
> >>> On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
>
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> Konstantin
> Sent: Thursday, 17 June 2021 19.06
>
> I think it would be better to change rx_pkt_burst() to accept port_id
> and queue_id, instead of void *.
Current:
typedef uint16_t (*eth_rx_burst_t)(void *rxq,
On 6/17/2021 5:55 PM, Morten Brørup wrote:
>> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ferruh Yigit
>> Sent: Thursday, 17 June 2021 18.13
>>
>> On 6/17/2021 4:17 PM, Morten Brørup wrote:
From: Ananyev, Konstantin [mailto:konstantin.anan...@intel.com]
Sent: Thursday, 17 June 20
On 6/17/2021 6:05 PM, Ananyev, Konstantin wrote:
>
>
>> On 6/17/2021 4:17 PM, Morten Brørup wrote:
From: Ananyev, Konstantin [mailto:konstantin.anan...@intel.com]
Sent: Thursday, 17 June 2021 16.59
14/06/2021 15:15, Bruce Richardson:
> On Mon, Jun 14, 2021
> >
> > 14/06/2021 15:15, Bruce Richardson:
> >> On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Monday, 14 June 2021 12.59
>
> Performance of access in a f
On 6/18/2021 10:14 AM, Morten Brørup wrote:
>> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
>> Konstantin
>> Sent: Thursday, 17 June 2021 19.06
>>
>> I think it would be better to change rx_pkt_burst() to accept port_id
>> and queue_id, instead of void *.
>
> Current:
>
> typedef
On 6/18/2021 11:41 AM, Ananyev, Konstantin wrote:
>
>>>
>>> 14/06/2021 15:15, Bruce Richardson:
On Mon, Jun 14, 2021 at 02:22:42PM +0200, Morten Brørup wrote:
>> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
>> Sent: Monday, 14 June 2021 12.5
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ferruh Yigit
> Sent: Friday, 18 June 2021 12.47
>
> On 6/18/2021 10:14 AM, Morten Brørup wrote:
> > Another thing:
> >
> > I just noticed that struct rte_eth_dev_data has "void **rx_queues;"
> (and similarly for tx_queues).
> >
> > That should
Hi everyone,
> > >>> One more thought here - if we are talking about rte_ethdev[] in
> > >>> particular, I think we can:
> > >>> 1. move public function pointers (rx_pkt_burst(), etc.) from rte_ethdev
> > >>> into a separate flat array.
> > >>> We can keep it public to still use inline functi
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> Konstantin
>
> > > How can we hide the callbacks since they are used by inline burst
> functions.
> >
> > I probably I owe a better explanation to what I meant in first mail.
> > Otherwise it sounds confusing.
> > I'll try to write
>
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > Konstantin
> >
> > > > How can we hide the callbacks since they are used by inline burst
> > functions.
> > >
> > > I probably I owe a better explanation to what I meant in first mail.
> > > Otherwise it sounds confusing.
> >
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> Konstantin
>
> >
> > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > > Konstantin
> > >
> > > > > How can we hide the callbacks since they are used by inline
> burst
> > > functions.
> > > >
> > > > I probably I
On 6/21/2021 12:06 PM, Ananyev, Konstantin wrote:
>
> Hi everyone,
>
>> One more thought here - if we are talking about rte_ethdev[] in
>> particular, I think we can:
>> 1. move public function pointers (rx_pkt_burst(), etc.) from rte_ethdev
>> into a separate flat array.
>
On 6/21/2021 1:30 PM, Ananyev, Konstantin wrote:
>
>>
>>> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
>>> Konstantin
>>>
> How can we hide the callbacks since they are used by inline burst
>>> functions.
I probably I owe a better explanation to what I meant in first
>
> On 6/21/2021 1:30 PM, Ananyev, Konstantin wrote:
> >
> >>
> >>> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> >>> Konstantin
> >>>
> > How can we hide the callbacks since they are used by inline burst
> >>> functions.
>
> I probably I owe a better explanation t
> >> One more thought here - if we are talking about rte_ethdev[] in
> >> particular, I think we can:
> >> 1. move public function pointers (rx_pkt_burst(), etc.) from
> >> rte_ethdev into a separate flat array.
> >> We can keep it public to still use inline functions for 'f
On 6/21/2021 3:42 PM, Ananyev, Konstantin wrote:
>
One more thought here - if we are talking about rte_ethdev[] in
particular, I think we can:
1. move public function pointers (rx_pkt_burst(), etc.) from
rte_ethdev into a separate flat array.
We can
>
> On 6/21/2021 3:42 PM, Ananyev, Konstantin wrote:
> >
> One more thought here - if we are talking about rte_ethdev[] in
> particular, I think we can:
> 1. move public function pointers (rx_pkt_burst(), etc.) from
> rte_ethdev into a separate flat array.
>
On 6/21/2021 3:38 PM, Ananyev, Konstantin wrote:
>
>>
>> On 6/21/2021 1:30 PM, Ananyev, Konstantin wrote:
>>>
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> Konstantin
>
>>> How can we hide the callbacks since they are used by inline burst
> functions.
>
>
> On 6/21/2021 3:38 PM, Ananyev, Konstantin wrote:
> >
> >>
> >> On 6/21/2021 1:30 PM, Ananyev, Konstantin wrote:
> >>>
>
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > Konstantin
> >
> >>> How can we hide the callbacks since they are used by inline
>
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > Konstantin
> >
> > >
> > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > > > Konstantin
> > > >
> > > > > > How can we hide the callbacks since they are used by inline
> > burst
> > > > functions.
> > > >
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> Konstantin
>
> >
> > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > > Konstantin
> > >
> > > >
> > > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > > > > Konstantin
> > > > >
> > > > > > >
>
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > Konstantin
> >
> > >
> > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > > > Konstantin
> > > >
> > > > >
> > > > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > > > > > Konstantin
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> Konstantin
>
> >
> > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > > Konstantin
> > >
> > > >
> > > > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ananyev,
> > > > > Konstantin
> > > > >
> > > > > >
>
61 matches
Mail list logo
