The sFlow mechanism is OVS is inherently ingress-only sampling, so
per-port config would rarely make sense as it would result in only
half the picture for a given VM or link. The sFlow philosophy is to
keep the agent as simple as possible and generate a standard feed that
can be used by more
On 3/23/2019 2:28 AM, Ammu wrote:
Hey Greg,
The recent check with OVS 2.10.1 version was done with CentOS Linux
release 7.3.1611
But, I will have to support the solution with distributions CentOS/Red
Hat/Ubuntu.
Currently giving you the output of distribution CentOS alone.
On 3/24/2019 5:25 PM, Manuel Sopena Ballesteros wrote:
thank you very much Gregory,
I am already preparing an email to Tariq. Could I CC you in that email?
Sure, that's fine by me.
- Greg
thank you
From: Gregory Rose [gvrose8...@gmail.com]
Sent:
Hello
In the meantime, two related questions:
- Would github releases be safe to use? For exmaple
https://github.com/openvswitch/ovs/archive/v2.5.7.tar.gz
- Is 2.5.7 going to replace 2.5.6 as LTS release?
BR
Jaime.
-Original Message-
From: Ben Pfaff
To: Justin Pettit ,
Hi,
Thanks all! I will start working on it pretty soon then.
> Lucas, I support you moving forward with 1), because:
> a) it is more simple and straightforward, yet the configuration on
> chassis won't (shouldn't) create compatibility issue
> b) it doesn't conflict with further optimization with
Hi,
Per below OVS document, we can configure per bridge sflow.
http://docs.openvswitch.org/en/latest/howto/sflow/
$ ovs-vsctl -- --id=@sflow create sflow agent=${AGENT_IP} \
target="\"${COLLECTOR_IP}:${COLLECTOR_PORT}\"" header=${HEADER_BYTES} \
sampling=${SAMPLING_N}
Sorry , I forgot to mention I am using dpdk - 17.05 and OVS - 2.8.1
Thanks
Krish
On Mon, Mar 25, 2019 at 2:07 PM Krish wrote:
> Hi
>
> I am wondering why does batch execution takes more time than EMC and
> fast_path processing even if there are 32 packets grouped together from a
> same flow.
>
Hi
I am wondering why does batch execution takes more time than EMC and
fast_path processing even if there are 32 packets grouped together from a
same flow.
I am using iperf as a packet generation testing tool.
EMC processing -> 2~3 ms (32 packets)
Fast path -> .3 ms
packet_execution -> 20~30
