Re: [dpdk-dev] ebpf support in dpdk

On Fri, Apr 21, 2017 at 5:18 PM, Gal Sagie wrote: > I have a feeling you are talking about P4 ​well, not p4, but more specifically 'protocol-oblivious-forwarding' (POF). ebpf can describe both match+action rules on dpdk... -- kind regards anupam In the beginning was the la

[dpdk-dev] ebpf support in dpdk

hi all, i was just wondering if there are plans on adding ebpf support in dpdk ? imho, it would be pretty useful, among other things, in creating generic (protocol oblivious) match+action support in dpdk based forwarding elements. -- thank you kind regards anupam In the beginning was the

[dpdk-dev] acl: delete/modify rule support

t-trie?s. to conserve memory, rules are split into multiple non-overlapping/non-intersecting rules. i would wager that implementing deletion would be non-trivial :) better option might be to add/modify/delete your rule-list, and rebuild, and then re-use... ?-- kind regards anupam? In the beginning w

[dpdk-dev] Manual link speed/duplex configuration not working with DPDK

d no maintainer identified. since the latter is now there, the former can be resent ? ?-- thanks anupam? -- In the beginning was the lambda, and the lambda was with Emacs, and Emacs was the lambda.

[dpdk-dev] Huge ring allocation

hod of | allocating huge pages as memory has not yet become fragmented. ` --- thanks anupam

[dpdk-dev] [Crypto-API query]

r-crypto-pmd... for more information take a look here: http://dpdk.readthedocs.io/en/v16.04/cryptodevs/index.html -- thanks anupam

[dpdk-dev] [Crypto-API query]

ve sw-only crypto devices... --- thanks anupam

[dpdk-dev] [PATCH] e1000/base: Add missing braces to the 'if' statements

On Thu, Jun 23, 2016 at 4:04 PM, Markos Chandras wrote: > I have seen your commit, but my patch fixes a different file (although the > fix is similar). > > Am I missing something? > ?ah no. my bad. sorry about that. ?-- thanks anupam?

[dpdk-dev] [PATCH] e1000/base: Add missing braces to the 'if' statements

hi markos, please see : cba50f6be0db9efdf694dcf4bce4a6945a275182, which should already fix this. -- thanks anupam On Thu, Jun 23, 2016 at 2:55 PM, Markos Chandras wrote: > Add the missing braces to the 'if' statements to fix the misleading > identation. This also fixes the

[dpdk-dev] [PATCH 3/3] app/pdump: fix string overflow

dev last byte is NULL? why not just use a snprintf(...) here since it has better error behavior ? although compared to str*cpy it might be a bit slow, but hopefully that should be ok ? -- thanks anupam On Tue, Jun 21, 2016 at 10:51 PM, Ferruh Yigit wrote: > On 6/21/2016 4:18 PM, Reshma

[dpdk-dev] regarding coverity-scan-id : 127350

data.en_v1.device buffer which is also DEVICE_ID_SIZE bytes long. -- thanks anupam

[dpdk-dev] [PATCH] kni : fix build errors for gcc --version >= 6.1

This commit fixes build errors triggered due misleading indentation. Fixes: 38db3f7f50bde (e1000: update base driver) Fixes: 3fc5ca2f63529 (kni: initial import) Signed-off-by: Anupam Kapoor --- lib/librte_eal/linuxapp/kni/ethtool/igb/e1000_phy.c | 6 -- lib/librte_eal/linuxapp/kni

[dpdk-dev] [PATCH] kni : fix build errors for gcc --version >= 6.1

On Tue, Jun 21, 2016 at 3:40 PM, Ferruh Yigit wrote: > Hi Anupam, > > Thank you for the patch. > > > On 6/21/2016 9:37 AM, Anupam Kapoor wrote: > > This commit fixes build errors triggered due misleading indentation. > > > > Fixes: 366113dbfb696 (e1000: sup

[dpdk-dev] [DPDK16.04: Error While compiling]

>>>>> [2016-06-21T15:12:27+0530]: "amartya.das" (amarty-das): ,[ amartya-das ] | Its VM fedora21, gcc 4.9. ` does your vcpu support sse3 ? --- thanks anupam

[dpdk-dev] [PATCH] kni : fix build errors for gcc --version >= 6.1

This commit fixes build errors triggered due misleading indentation. Fixes: 366113dbfb696 (e1000: suppress misleading indentation warning) Signed-off-by: Anupam Kapoor --- lib/librte_eal/linuxapp/kni/ethtool/igb/e1000_phy.c | 12 lib/librte_eal/linuxapp/kni/ethtool/ixgbe

[dpdk-dev] build error on git checkout

9 CEST 2016 x86_64 GNU/Linux dpdk-devel% dpdk-devel% gcc --version gcc (GCC) 6.1.1 20160602 Copyright (C) 2016 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- thanks anupam