Hi,
i) Is pdcp ciphering / deciphering using rte_security API for PDCP possible
using Intel Crypto buffer ? Or it is required h/w offload to cryptodev
which supports PDCP ciphering/deciphering ? I understand that API sequence
given here mentio h/w offload ?
ii) In other words want to check, is the
Hi,
Please use this link for subscription
https://mails.dpdk.org/listinfo/dev#:~:text=To%20post%20a%20message%20to,subscription%2C%20in%20the%20sections%20below.&text=Subscribe%20to%20dev%20by%20filling,others%20from%20gratuitously%20subscribing%20you
.
or google for dpdk dev subscription.
Chee
ription request.
>
> Can you let me know if my request can be confirmed ?
>
> Regards,
>
> Nandini
>
>
>
> *From: *Venumadhav Josyula
> *Date: *Wednesday, October 28, 2020 at 9:34 PM
> *To: *Nandini Rangaswamy
> *Cc: *dev@dpdk.org , Sachchidanand Vaidya <
>
‘rte_eal_get_physmem_free’ for the we wanted
to submit patch.
Thanks,
Regards
Venumadhav
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Burakov, Anatoly
Sent: Friday, March 09, 2018 2:36 PM
To: Venumadhav Josyula ; dev@dpdk.org
Subject: Re: [dpdk-dev] Api in dpdk to get total free physical memory
On 08-Mar
Hi All,
Like 'rte_eal_get_physmem_size' api to the total size of the physical memory.
Is there an API to get to get total free memory physical memory available ?
We want such API we are planning to implement such API for the same
/* get the total size of memory */
uint64_t
rte_eal_get_physmem_f
Hi All,
Like ‘rte_eal_get_physmem_size’ api to the total size of the physical
memory. Is there an API to get to get total free memory physical memory
available ?
We want such API we are planning to implement such API for the same
/* get the total size of memory */
uint64_t
rte_eal_get_ph
Hi All,
Idea is following
- create lpm in one process where only rte_lpm and bare minimum is
acessible. Addition into this table will also happen in this process
context.
- Now in the packet processing context based ip of packet the lookup
will happen in the lpm created.
Is above possible.
Hi ,
We are using 'rte_mempool_create' for allocation of flow memory. This has
been there for a while. We just migrated to dpdk-18.11 from dpdk-17.05. Now
here is problem statement
Problem statement :
In new dpdk ( 18.11 ), the 'rte_mempool_create' take approximately ~4.4 sec
for allocation compar
Hi,
Few more points
Operating system : Centos 7.6
Logging mechanism : syslog
We have logged using syslog before the call and syslog after the call.
Thanks & Regards
Venu
On Wed, 13 Nov 2019 at 10:37, Venumadhav Josyula wrote:
> Hi ,
> We are using 'rte_mempool_create
530, Venumadhav Josyula wrote:
> > Hi,
> >
> > Few more points
> >
> > Operating system : Centos 7.6
> > Logging mechanism : syslog
> >
> > We have logged using syslog before the call and syslog after the call.
> >
> > Thanks & Reg
Hi Anatoly,
By default w/o specifying --iova-mode option is iova-mode=pa by default ?
Thanks
Venu
On Wed, 13 Nov, 2019, 10:56 pm Burakov, Anatoly,
wrote:
> On 13-Nov-19 9:19 AM, Bruce Richardson wrote:
> > On Wed, Nov 13, 2019 at 10:37:57AM +0530, Venumadhav Josyula wrote:
> >
d, Nov 13, 2019 at 10:37:57AM +0530, Venumadhav Josyula wrote:
> >> Hi ,
> >> We are using 'rte_mempool_create' for allocation of flow memory. This
> has
> >> been there for a while. We just migrated to dpdk-18.11 from dpdk-17.05.
> Now
> >> here i
ved
Thanks and regards
Venu
On Thu, 14 Nov 2019 at 15:14, Burakov, Anatoly
wrote:
> On 13-Nov-19 9:01 PM, Venumadhav Josyula wrote:
> > Hi Anatoly,
> >
> > By default w/o specifying --iova-mode option is iova-mode=pa by default ?
> >
> > Thanks
> > Venu
Hi Anatoly,
> I would also suggest using --limit-mem if you desire to limit the
> maximum amount of memory DPDK will be able to allocate.
We are already using that.
Thanks and regards,
Venu
On Thu, 14 Nov 2019 at 15:19, Burakov, Anatoly
wrote:
> On 14-Nov-19 8:12 AM, Venumadhav Josy
gards,
Venu
On Thu, 14 Nov 2019 at 15:27, Burakov, Anatoly
wrote:
> On 14-Nov-19 9:50 AM, Venumadhav Josyula wrote:
> > Hi Anatoly,
> >
> > Thanks for quick response. We want to understand, if there will be
> > performance implications because of iova-mode bei
PL note I am using dpdk 18-11...
On Wed, 13 Nov, 2019, 10:37 am Venumadhav Josyula,
wrote:
> Hi ,
> We are using 'rte_mempool_create' for allocation of flow memory. This has
> been there for a while. We just migrated to dpdk-18.11 from dpdk-17.05. Now
> here is problem
We are seeing following error, no device is detected
==
EAL: Detected 8 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI de
the that IOMMU type selection is failing, is it possible
to somehow default it to either igb_uio ?
Thanks,
Regards,
Venu
On Thu, 28 Nov 2019 at 13:09, Gavin Hu (Arm Technology China) <
gavin...@arm.com> wrote:
> Hi Venumadhav,
>
> > -Original Message-
> > From: dev
Hi Hui,
I understand that and we are exploring that.
But is there no work around there where in it defaults to igb_uio driver
something like that. Basic idea is we should not be situation of no
port detected at all under this situation ?
Thanks,
Regards,
Venu
On Thu, 28 Nov 2019 at 13:15, H
- Lee
>
> -Original Message-
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Hui Wei
> Sent: Thursday, November 28, 2019 1:01 AM
> To: Venumadhav Josyula
> Cc: dev ; users ; Venumadhav Josyula <
> vjosy...@parallelwireless.com>
> Sub
Hi Anatoly,
I was able to resolve the problem, which problem in our script.
Thanks and regards
Venu
On Fri, 6 Dec 2019 at 16:17, Burakov, Anatoly
wrote:
> On 18-Nov-19 4:43 PM, Venumadhav Josyula wrote:
> > Hi Anatoly,
> >
> > After using iova-mode=va, i see my ports are
Hi All,
We are observing packet drops ~@90Mbs with virtio pmd driver. These packets
are not been
queued in the tx descriptors, the function 'rte_eth_tx_burst' is returning
the less than n.
So questions are following
i) are there any issues seen ?
Observations in our case :-
i) packets are dropp
22 matches
Mail list logo