> -Original Message-
> From: Thomas Monjalon
> Sent: Thursday, January 20, 2022 8:28 PM
> To: Rohit Raj
> Cc: Bruce Richardson ; Ray Kinsella
> ; Dmitry Kozlyuk ; Narcisa Ana
> Maria Vasile ; Dmitry Malloy
> ; Pallavi Kadam ;
> dev@dpdk.org; Nipun Gupta
these hardware specific buses.
So, to close these devices, we need a new API which can do this for us. That is
why "rte_bus_close" is required.
Regards,
Rohit Raj
> -Original Message-
> From: Thomas Monjalon
> Sent: Wednesday, January 19, 2022 4:02 PM
> To: Rohit R
From: Rohit Raj
This patch add support for closing the bus objects which
were acquired In the bus probe.
Some devices need to be cleaned while in both primary and
secondary process and while some need to be cleaned only in
case of primary process.
The devices are closed as per the white list
From: Rohit Raj
As per the current code we have API for bus probe, but the
bus close API is missing. This breaks the multi process
scenarios as objects are not cleaned while terminating the
secondary processes.
This patch adds a new API rte_bus_close() for cleanup of
bus objects which were
> -Original Message-
> From: Ananyev, Konstantin
> Sent: Friday, November 12, 2021 3:11 PM
> To: Rohit Raj ; dev@dpdk.org; Yigit, Ferruh
>
> Cc: Nipun Gupta ; Sachin Saxena
> ; Vanshika Shukla
> Subject: [EXT] RE: [PATCH v2] examples/l3fwd: fix jumbo packet drop
From: Rohit Raj
l3fwd uses mbufs with 2KB data size. If we enable jumbo packets, it is
not able to store packets with size greater than 2KB, hence these
packets are dropped.
This patch fixes this issue by enabling scatter for jumbo packet, if
it is supported by NIC.
If scatter is not supported
> -Original Message-
> From: Ferruh Yigit
> Sent: Wednesday, August 11, 2021 5:01 PM
> To: Rohit Raj
> Cc: dev@dpdk.org; Nipun Gupta ; Hemant Agrawal
> ; Sachin Saxena ;
> Vanshika Shukla
> Subject: Re: [dpdk-dev] [PATCH v1] examples/l3fwd: fix jumbo packet d
From: Rohit Raj
l3fwd uses mbufs with 2KB data size. If we enable jumbo packets, it is
not able to store packets with size greater than 2KB, hence these
packets are dropped.
This patch fixes this issue by enabling scatter for jumbo packet, if
it is supported by NIC.
If scatter is not supported
Hi Ferruh,
Sorry, I missed you comment last time. I will send an updated patch series
after taking care of your suggested changes.
Regards,
Rohit Raj
Software Engineer | NXP India Private Limited
Sent from Outlook Mobile
From: Ferruh Yigit
Sent: Thursday
From: Rohit Raj
This patch add support for closing the bus objects which
were acquired In the bus probe.
Some devices need to be cleaned while in both primary and
secondary process and while some need to be cleaned only in
case of primary process.
The devices are closed as per the white list
From: Rohit Raj
As per the current code we have API for bus probe, but the
bus close API is missing. This breaks the multi process
scenarios as objects are not cleaned while terminating the
secondary processes.
This patch adds a new API rte_bus_close() for cleanup of
bus objects which were
From: Rohit Raj
Added support for rte_bus_close API on windows to reset the devices on
the bus to default state.
Signed-off-by: Rohit Raj
---
lib/librte_eal/windows/eal.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/librte_eal/windows/eal.c b/lib/librte_eal/windows
From: Rohit Raj
Added support for rte_bus_close API on freebsd to reset the devices on
the bus to default state.
Signed-off-by: Rohit Raj
---
lib/librte_eal/freebsd/eal.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/librte_eal/freebsd/eal.c b/lib/librte_eal/freebsd/eal.c
index
From: Rohit Raj
Certain bus objects may need to be closed and re-acquired
while terminating and rerunning the client application.
Hence a signal handler is required to catch the termination
of the App and hence closing the bus objects.
This patch adds the missing signal handler in the client
From: Rohit Raj
As per the current code we have API for bus probe, but the
bus close API is missing. This breaks the multi process
scenarios as objects are not cleaned while terminating the
secondary processes.
This patch adds a new API rte_bus_close() for cleanup of
bus objects which were
From: Rohit Raj
This patch add support for closing the bus objects which
were acquired In the bus probe.
Some devices need to be cleaned while in both primary and
secondary process and while some need to be cleaned only in
case of primary process.
The devices are closed as per the white list
From: Rohit Raj
Certain bus objects may need to be closed and re-acquired
while terminating and rerunning the client application.
Hence a signal handler is required to catch the termination
of the App and hence closing the bus objects.
This patch adds the missing signal handler in the client
From: Rohit Raj
This patch add support for closing the bus objects which
were acquired In the bus probe.
Some devices need to be cleaned while in both primary and
secondary process and while some need to be cleaned only in
case of primary process.
The devices are closed as per the white list
From: Rohit Raj
Certain bus objects may need to be closed and re-acquired
while terminating and rerunning the client application.
Hence a signal handler is required to catch the termination
of the App and hence closing the bus objects.
This patch adds the missing signal handler in the client
From: Rohit Raj
As per the current code we have API for bus probe, but the
bus close API is missing. This breaks the multi process
scenarios as objects are not cleaned while terminating the
secondary processes.
This patch adds a new API rte_bus_close() for cleanup of
bus objects which were
Yes, I agree.
I will rework and send this patch series again.
Regards,
Rohit Raj
Software Engineer | NXP India Private Limited
Email: rohit@nxp.com
-Original Message-
From: Stephen Hemminger
Sent: Tuesday, July 28, 2020 10:54 PM
To: Rohit Raj
Cc: Ray Kinsella ; Neil Horman ;
dev
From: Rohit Raj
This patch add support for closing the bus objects which
were acquired In the bus probe.
Some devices need to be cleaned while in both primary and
secondary process and while some need to be cleaned only in
case of primary process.
The devices are closed as per the white list
From: Rohit Raj
As per the current code we have API for bus probe, but the
bus close API is missing. This breaks the multi process
scenarios as objects are not cleaned while terminating the
secondary processes.
This patch adds a new API rte_bus_close() for cleanup of
bus objects which were
From: Rohit Raj
Certain bus objects may need to be closed and re-acquired
while terminating and rerunning the client application.
Hence a signal handler is required to catch the termination
of the App and hence closing the bus objects.
This patch adds the missing signal handler in the client
From: Rohit Raj
The current state of the DPIO object should be checked
before trying to close/disable the object.
Fixes: 293c0ca94c36 ("bus/fslmc: support memory backed portals with QBMAN 5.0")
Cc: sta...@dpdk.org
Signed-off-by: Rohit Raj
---
drivers/bus/fslmc/portal/dpaa2_hw_
25 matches
Mail list logo
