Hi,
We were converting the acl rule data, from host to network byte order, [by
mistake] while inserting into trie. And while searching we are not converting
the search data to n/w byte order.
With the above also rules are matching, except few scenarios.
After correcting the above mistake, all r
Hi All,
When I'm trying to configure some 5000+ ACL rules with different source IP
addresses, getting ACL memory allocation failure.\
[root at ACLISSUE log_2015_10_26_08_19_42]# vim np.log
match nodes/bytes used: 816/104448
total: 12940832 bytes
ACL: Build phase for ACL "ipv4_acl_table2":
memory
Hi All,
When I'm trying to configure some 5000+ ACL rules with different source IP
addresses, getting ACL memory allocation failure. I'm using DPDK 2.1.
[root at ACLISSUE log_2015_10_26_08_19_42]# vim np.log
match nodes/bytes used: 816/104448
total: 12940832 bytes
ACL: Build phase for ACL "ipv4_
l Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Rapelly, Varun
> Sent: Friday, February 26, 2016 10:28 AM
> To: dev at dpdk.org
> Subject: Re: [dpdk-dev] ACL memory allocation failures
>
> Hi All,
>
> When I'm trying to configure some 5000+ ACL r
me);
return -ENOMEM;
}
Konstantin
>
> > -Original Message-
> > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Rapelly, Varun
> > Sent: Friday, February 26, 2016 10:28 AM
> > To: dev at dpdk.org
> > Subject: Re: [dpdk-dev] ACL memor
total_size, ctx->socket_id, ctx->name);
return -ENOMEM;
}
>>> Is there any way to reserve some particular amount of huge page memory for
>>> ACL trie (in eal_init())?
Konstantin
>
> > -Original Message-
> > From: dev [mail
Hi,
struct ipv6_5tuple {
uint8_t proto; /* Protocol, next header. */
uint32_t src_addr0; /* IP address of source host. */
uint32_t src_addr1; /* IP address of source host. */
uint32_t src_addr2; /* IP address of source host. */
uint32_t src_addr3; /* IP address of source
Hi All,
I'm facing the following issue when testing testpmd application.
EAL: PCI device :03:00.0 on NUMA socket -1
EAL: probe driver: 15ad:7b0 rte_vmxnet3_pmd
EAL: :03:00.0 not managed by UIO driver, skipping
EAL: PCI device :0b:00.0 on NUMA socket -1
EAL: probe driver: 15ad:7b
Hi All,
I'm facing the following issue when testing testpmd application with DPDK-1.8.0.
EAL: PCI device :03:00.0 on NUMA socket -1
EAL: probe driver: 15ad:7b0 rte_vmxnet3_pmd
EAL: :03:00.0 not managed by UIO driver, skipping
EAL: PCI device :0b:00.0 on NUMA socket -1
EAL: prob
directions to resolve this issue.
Regards,
Varun
-Original Message-
From: Bruce Richardson [mailto:bruce.richard...@intel.com]
Sent: Friday, March 20, 2015 7:33 PM
To: Rapelly, Varun
Cc: dev at dpdk.org
Subject: Re: [dpdk-dev] Testpmd application failing with Cause: No probed
ethernet device with DP
Hi,
I'm facing problems with "iommu=pt intel_iommu=on" in ProLiant DL380p Gen8
server[RHEL 7.1]. But on ProLiant DL380 G7[RHEL 7.1] server, not facing this
issue.
When I add the above options to the kernel boot line and configure OVS bridge
[with -dpdk option], not able to send the packets out
Hi All,
I'm not able to send packets through OVS bridge [with dpdk] when iommu is
enabled on HP DL380 G8 [RHEL 7.1]. Getting following errors in dmesg.
[0.657681] IOMMU: Setting identity map for device :01:00.2 [0xbdff6000
- 0xbdffcfff]
[0.657686] IOMMU: Prepare 0-16MiB unity mappin
: Friday, July 24, 2015 2:47 PM
To: Rapelly, Varun
Cc: dev at dpdk.org
Subject: Re: [dpdk-dev] iommu Error on DL380 G8 with RHEL 7.1
On 24/07/2015 09:54, Rapelly, Varun wrote:
> Hi All,
>
> I'm not able to send packets through OVS bridge [with dpdk] when iommu is
> enabled on HP D
Hi Monroy,
Thanks for the reply :)
Ok Will check with Lee.
-Original Message-
From: Gonzalez Monroy, Sergio [mailto:sergio.gonzalez.mon...@intel.com]
Sent: Friday, July 24, 2015 2:47 PM
To: Rapelly, Varun
Cc: dev at dpdk.org
Subject: Re: [dpdk-dev] iommu Error on DL380 G8 with RHEL 7.1
Hi All,
Can we build ACL trie in following way [lets say 4000 rules]: [I'm using DPDK
2.1.0]
1. Create context
2. Add 1000 rules, to the context [rte_acl_add_rules]
3. Then build the trie [rte_acl_build]for 1000 rules.
4. Then repeat the steps 2-3 for the remaining 300
Hi,
We are facing a problem in DPDK - AF_PACKET poll mode driver.
We are able to create RAW socket and receive RTP-Signaling packets successfully
and our application is running fine.
But if we try doing scp to the same interface we are facing a crash.
The stack trace:
(gdb) bt
#0 __memcpy_ss
16 matches
Mail list logo