hello all,
I'd like to know the usecases and usage of the following commands because I
think they are related to QoS function.
Are there any usecases or operation samples?
- policer : https://docs.fd.io/vpp/18.07/clicmd_src_vnet_policer.html
- qos :
All,
A first pass at the release notes for VPP 18.04 are available for review in
https://gerrit.fd.io/r/#/c/12038/ . I have not yet walked the commit history
looking for juicy key features to include in the list, I'll do that tomorrow.
Suggestions are, of course, welcome!
A preview can be
any suggestions?
Thanks
Hi Damjan,
I would say there is nothing we can do but to drop the packets. Developers have
to take care of how to use handoff mechanism. In our case or NAT case, it has
to be ‘no wait’, while it could be ‘wait forever’ in a stream line mode –
worker A -> B -> C.
BTW, my colleague Lollita
I’m not aware of such activities, but before you start working on the actual
implementation i would suggest community discussion on architecture, use cases
and required changes in the code. Biweekly community call is likely good forum
for that.
—
Damjan
> On 22 Apr 2018, at 07:17, Andrew
Hi all,
We were wondering if anyone is currently working on getting VPP to
work with the DPDK eventdev? We don't want to duplication.
Thanks,
Andrew
-=-=-=-=-=-=-=-=-=-=-=-
Links:
You receive all messages sent to this group.
View/Reply Online (#9032):
Hi
I want to set qos parameters according to this tutorial [1], but i
couldn't find the file for port, subport and pipe configurations. Can
you please help me in this matter?
Best regards
Reza
Links:
--
[1] https://docs.fd.io/vpp/16.12/qos_doc.html
All,
A reminder that VPP 18.04 will be released this Wednesday, April 25th.
We're still accepting critical bug fixes, but at this point I expect few
patches between now and then. That said, feedback on the stability of the
branch is always welcome.
Cheers,
Chris.
Hi,
Please try:
https://gerrit.fd.io/r/12014
you don’t need a next=hop when specifying an L2 receive path, so:
mpls local-label add eos 1023 via l2-input-on mpls-tunnel0
regards,
neale
From: on behalf of "omid via Lists.Fd.Io"
HI Xyxue,
Can you please test to see if the situation improves with:
https://gerrit.fd.io/r/#/c/12012/
thanks,
neale
From: on behalf of xyxue
Date: Friday, 20 April 2018 at 11:31
To: "vpp-dev@lists.fd.io"
Subject: [vpp-dev]
Dear Kingwel,
What would you expect from us to do if A waits for B to take stuff from the
queue and on the same time
B waits for A for the same reason beside what we already do in NAT code, and
that is to drop instead of wait.
--
Damjan
On 23 Apr 2018, at 14:14, Kingwel Xie
Hi Ole, Damjan,
Thanks, for the comments.
But I’m afraid this is the typical case that workers handoff to each other if
we don’t want to create an I/O thread which might become the bottleneck in the
end.
Regards,
Kingwel
From: Damjan Marion (damarion) [mailto:damar...@cisco.com]
Sent:
Kingwei,
Yes, it's possible to dead lock in this case.
We had a similar issue with the NAT implementation. While testing I think we
ended up dropping when the queue was full.
Best regards,
Ole
> On 23 Apr 2018, at 10:33, Kingwel Xie wrote:
>
> Hi Damjan and all,
>
Hi Damjan and all,
We are currently thinking of how to utilize the handoff mechanism to serve our
application logic – to run a packet re-ordering and re-transmit queue in the
same worker context to avoid any lock between threads. We come across with a
question when looking into the
Did you delete the handle of the shared memory? These two files:
/dev/shm/global_vm vpe-api
The mheap header structure is changed, so you have to ask vPP to re-create the
shared memory heap.
Sorry, I forgot to mention that before.
From: 薛欣颖 [mailto:xy...@fiberhome.com]
Sent: Monday, April
Hi, I configure vpls with following commands:
VPLS configuration: MPLS L2VPN VPLS PE1
1.create host-interface name eth0 2.create host-interface name eth1 3.set int
state host-eth1 up 4.set int state host-eth0 up 5.set interface mac address
host-eth0
Hi Kingwel,
After I merged the three patch ,there is a SIGSEGV when I startup vpp (not
every time). And the error didn't appear before .
Is there anything I can do to fix it?
Program received signal SIGSEGV, Segmentation fault.
clib_mem_alloc_aligned_at_offset (size=54, align=4,
I'll clarify my question
For a PCI device e.g. :04:00:0 - is it possible to add this device to VPP
on runtime with a specific cli command ?
Currently I only can add these kind of devices by specifying it in the
while-list in startup.conf
Best Regards
Avi
> -Original Message-
>
18 matches
Mail list logo