Hi,
I am looking to understand when ‘punt’ option is used in “ set interface state
[up | down | punt | enable] “ . The command description says that
it is used to punt traffic to slow-path and not used for forwarding. Looking to
understand more about what this means. I am trying to explore if
Disabling a feature on an interface will not change the graph arcs, as stated
by Dave. The more relevant CLI is to use “show interface features
” to check whether a particular feature is enabled on an
interface or not.–John
From: vpp-dev@lists.fd.io On Behalf Of Dave Barach via
Lists.Fd.I
No, there isn’t. There isn’t much of a point in deleting graph arcs. If the
feature is reenabled, the existing arc from A to B will be reused.
D.
From: vpp-dev@lists.fd.io On Behalf Of Andrew Yourtchenko
Sent: Tuesday, September 4, 2018 2:50 PM
To: .ılı.D'p@k.ılı.
Cc: vpp-dev@lists.fd.io
Subje
Hi Deepak,
Not, as far as my quick code browse suggests.
—a
> On 4 Sep 2018, at 20:25, .ılı.D'p@k.ılı. wrote:
>
> Hi Andrew,
>
> Is there a similar delete call for the "vlib_node_add_next" function?
>
> Regards
> Deepak Kumar Ch
>
>
>> On Tue, Sep 4, 2018 at 11:54 PM, .ılı.D'p@k.ılı.
>>
Hi Andrew,
I was expecting the delete command to remove acl from the ip4 arc and also
the node graph of acl wont have ip4-lookup listed in its next nodes.
The current delete command is not doing a revert to old state.
Is there a way to make the node-graph go back to the init state?
Regards,
Deep
Hi Andrew,
Is there a similar delete call for the "vlib_node_add_next" function?
Regards
Deepak Kumar Ch
On Tue, Sep 4, 2018 at 11:54 PM, .ılı.D'p@k.ılı.
wrote:
> Hi Andrew,
>
> I was expecting the delete command to remove acl from the ip4 arc and also
> the node graph of acl wont have ip4-l
You can send the patch now to vpp/master … master is open for business :)
18.07 is on the stable/1807 branch :)
Ed
On September 4, 2018 at 12:24:52 PM, Gonsalves, Avinash (Nokia -
IN/Bangalore) (avinash.gonsal...@nokia.com) wrote:
Done. Will send the patch for review after 18.07.1 is out.
-
Done. Will send the patch for review after 18.07.1 is out.
-Avinash
From: Ed Warnicke
Sent: Tuesday, September 04, 2018 10:52 PM
To: Damjan Marion via Lists.Fd.Io ; dmar...@me.com;
Gonsalves, Avinash (Nokia - IN/Bangalore)
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] 18.07.1 dot release
Sec
Second that… bug fixes in 18.07.1… new features on master for 18.10
Ed
On September 4, 2018 at 12:21:28 PM, Damjan Marion via Lists.Fd.Io (
dmarion=me@lists.fd.io) wrote:
Dear Avinash,
Dot releases are only for bug fixes, new features should not go there...
--
Damjan
On 4 Sep 2018, at
Dear Avinash,
Dot releases are only for bug fixes, new features should not go there...
--
Damjan
> On 4 Sep 2018, at 18:12, avinash.gonsal...@nokia.com wrote:
>
> I would like to propose an enhancement for vpp to work with dpdk
> multicore-crypto scheduler
> (http://doc.dpdk.org/guides-18.0
Deepak,
If the feature enable/disable (or its usage) is broken, the trace for the
traffic via thar interface with removed acl would still show the acl plugin
node in the path, could you send the trace for a packet with acl and without
acl to see whether it is the case ?
I don’t make any effort
I would like to propose an enhancement for vpp to work with dpdk
multicore-crypto scheduler (
http://doc.dpdk.org/guides-18.02/cryptodevs/scheduler.html ).
For the software crypto pmd to be scheduled on multiple cores the following
dpdk configuration is required:
vdev
crypto_scheduler,slave=a
Dear Ping,
Can you please clean up your workspace (git clean -fdx) and then capture full
log...
Thanks,
--
Damjan
> On 4 Sep 2018, at 15:40, Yu, Ping wrote:
>
> Hi, Damjan,
>
> My Ubuntu environment is good. But in FC27, I got the following issue in
> debug mode.
>
>
> -- Build file
Hi ,
When i remove acl from interface, its node graph doesnt revert back to
original state.
#vppctl show vlib graph acl-plugin-in-ip4-fa
Name NextPrevious
acl-plugin-in-ip4-faerror-drop [0]
//ADD ACl
vat# acl_add_replace ipv4 permit
A number of fixes have been added to the stable/1807 branch since we cut
the 18.07 release. Several of them merit a dot release.
I’d like to be able to do an 18.07.1 dot release this week or next, and
wanted to open the discussion here for folks who may have fixes they
would like to see in that r
Hi, Damjan,
My Ubuntu environment is good. But in FC27, I got the following issue in debug
mode.
-- Build files have been written to:
/home/pyu4/git-home/vpp_master/vpp/build-root/build-vpp_debug-native/vpp
Building vpp in
/home/pyu4/git-home/vpp_master/vpp/build-root/build-vpp_debug-nat
Hi Stan,
Unfortunately I don’t have an ARM machine on to decode the post-mortem data.
Could you do this?
Thanks,
Neale
From: Stanislav Chlebec
Date: Tuesday, 4 September 2018 at 11:06
To: Stanislav Chlebec , "Neale Ranns (nranns)"
, "vpp-dev@lists.fd.io"
Subject: RE: [vpp-dev] Cavium Thunde
Hi Neale
Have you had the occasion to look at that api_post_mortem data?
Have you found the reason of crash?
Thanks
Stan
From: Stanislav Chlebec [mailto:stanislav.chle...@pantheon.tech]
Sent: Wednesday, August 22, 2018 3:39 PM
To: Neale Ranns (nranns) ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev]
18 matches
Mail list logo
