when boot vswitchd, we can pass log_file and log level as parameters, but it
seems these params only take effect for vswitchd itself, but not dpdk.
I can only see EAL logs in the console when launch vswitchd, but I can't see
any EAL logs in vswitchd.log and /var/log/syslog.
so is there any metho
uot; wrote:
>On 10/24/2016 11:55 AM, ychen wrote:
>> hi, I am a freshman to ovs DPDK, when I tried to launch ovs with dpdk
>> inited, I found that all the ovs threads are pinned to master lcore,
>> but I can't find any code for setting the affinity of the specified thread
hi, I am a freshman to ovs DPDK, when I tried to launch ovs with dpdk inited, I
found that all the ovs threads are pinned to master lcore,
but I can't find any code for setting the affinity of the specified thread.
Here is my configuration:
lscpu
Architecture: x86_64
CPU op-mode(s):
It is my fault, though the image version is 3.10.45, but I didn't update
package linux-libc-dev, it is still in version 3.2
After update package linux-libc-dev, the problem gone, and process
ovs-vswitched is up!
At 2016-09-28 10:03:10, "ychen" wrote:
some additional
eep debug shows that VFIO_PRESENT is not defined, but now my kernel
version is:
Linux 10-180-0-39 3.10.45-openstack-amd64, which is greater than 3.6.0
At 2016-09-27 21:36:27, "Aaron Conole" wrote:
>ychen writes:
>
>> hi,
>> I follow the doc "INSTALLDP
hi,
I follow the doc "INSTALLDPDK.md" to build ovs dpdk envrioment, but failed to
start ovs-vswitchd
here is my configurations:
1. kernel: 3.10.45-openstack-amd64 #1 SMP Tue Jul 1 01:52:20 UTC 2014 x86_64
GNU/Linux
2. NIC:
01:00.0 Ethernet controller [0200]: Intel Corporation 82599EB 10-Gigabit
t;row35edc309_3d4a_4791_8aae_ab3a1ac73aa8"]]],
"table":"Bridge",
"where":[["_uuid","==",["uuid","774222f2-9ab9-427f-a634-b818dc13cb2e"]]],
"op":"mutate"
}
At 2016-03-08 12:32:30, "Ben
hi:
I noticed that when add or delete port, the transaction always send op wait
with all the ports in the same bridge.
If the port p0 and p1 are totally independent, and have no relationship with
each other, why when I add port p1, I need to wait port p0?
__
"Ben Pfaff" wrote:
>On Thu, Aug 20, 2015 at 11:29:07AM +0800, ychen wrote:
>> port's ingress qdisc rule will automatically disappeared after
>> the following steps:
>> 1)use ip tuntap to create port tapA and tapB
>> 2)set tapA and tapB to ingress qdisc with linux
port's ingress qdisc rule will automatically disappeared after
the following steps:
1)use ip tuntap to create port tapA and tapB
2)set tapA and tapB to ingress qdisc with linux tc command
3)add tapA to ovs bridge
4)add tapB to the same ovs bridge(ingress rule disappear for tapA)
ingress_policing_ra
Hi:
when I read code about function netdev_linux_set_policing(), I'm puzzled with
flag VALID_POLICING.
it seems only when programs are in executing the code
"tc_add_del_ingress_qdisc" then the flag VALID_POLICING will be cleared.
this flag will always set whether users configured ingress po
none zero, then
VALID_POLICING should be set, if ingress_policing_rate is cleared or set to 0,
then VALID_POLICING should be unset
am I right? or there is another meaning of this flag?
At 2015-08-10 21:36:51, "ychen" wrote:
There are still something puzzled me, can you do some
12 matches
Mail list logo
