Hi Jason,
You are right but I've tried to work in multiple mode as well and it did
not change the result.
I hope this issue will be solved.
Thanks,
Shirley.
On Fri, Jan 20, 2017 at 9:48 PM, Jason Kwon wrote:
> Sorry to hijack the thread, but I was wondering, is the binding of the KNI
> kernel t
Sorry to hijack the thread, but I was wondering, is the binding of the KNI
kernel thread only applicable in multiple kthread mode? Does it apply in
single kernel thread mode? Looking at the 16.07.2 source, I saw the
following:
/**
* Create a new kernel thread for multiple mode,
Hi,
thanks for the quick answer.
I ran the same test with one kni port
with the following configuration:
sudo insmod rte_kni.ko lo_mode=lo_mode_fifo_skb
sudo ./kni -c 0xf -n 4 -- -P p 0x1 --config="(0,1,2,3)"
and transmitted towards the single port traffic with rate of 300Mbps.
as you can see be
On 1/17/2017 5:46 PM, Ferruh Yigit wrote:
> On 1/16/2017 2:58 PM, Shirley Avishour wrote:
>> I am currently using the kernel interface for recording the received
>> traffic by duplicating the received packets and sending a copy to the
>> kni (and performing pcap_open_live on the kni).
>> my goal ra
On 1/17/2017 12:34 PM, Shirley Avishour wrote:
> Hi,
> can the KNI_KTHREAD_RESCHEDULE_INTERVAL decrease to lower values than 5
> usecs?? is it effective at all?
You are right, it may not be since metric is usecs, and
usecs_to_jiffies() most probably will give same value for 5 and lower.
Removing
On 1/16/2017 2:58 PM, Shirley Avishour wrote:
> I am currently using the kernel interface for recording the received
> traffic by duplicating the received packets and sending a copy to the
> kni (and performing pcap_open_live on the kni).
> my goal rate is around 500Mbps. is it possible to achieve
On Mon, Jan 16, 2017 at 8:55 AM, Ferruh Yigit
wrote:
> On 1/16/2017 2:47 PM, Shirley Avishour wrote:
> > Hi,
> > As I wrote the kernel thread runs on a dedicated lcore.
> > running top while my application is running I see kni_single and the cpu
> > usage is really low...
> > Is there any rate li
Hi,
can the KNI_KTHREAD_RESCHEDULE_INTERVAL decrease to lower values than 5
usecs?? is it effective at all?
and what is the purpose of KNI_RX_LOOP_NUM? I am not sure I understand what
it does and what should I do with it to improve the performance.
thanks!
On Mon, Jan 16, 2017 at 5:43 PM, Shirley
Hi,
KNI_KTHREAD_RESCHEDULE_INTERVAL is currently set to 5usec. how should I
tweak this value to get better performance?
and can you explain the use of KNI_RX_LOOP_NUM and what can I possibly
modify it to ?
Thanks!
On Mon, Jan 16, 2017 at 4:55 PM, Ferruh Yigit
wrote:
> On 1/16/2017 2:47 PM, Shi
I am currently using the kernel interface for recording the received
traffic by duplicating the received packets and sending a copy to the kni
(and performing pcap_open_live on the kni).
my goal rate is around 500Mbps. is it possible to achieve it via the kni ??
On Mon, Jan 16, 2017 at 4:55 PM, F
On 1/16/2017 2:47 PM, Shirley Avishour wrote:
> Hi,
> As I wrote the kernel thread runs on a dedicated lcore.
> running top while my application is running I see kni_single and the cpu
> usage is really low...
> Is there any rate limitation for transmitting to the kernel interface
> (since packets
Hi,
As I wrote the kernel thread runs on a dedicated lcore.
running top while my application is running I see kni_single and the cpu
usage is really low...
Is there any rate limitation for transmitting to the kernel interface
(since packets are being copied in the kernel).
On Mon, Jan 16, 2017 at
On 1/16/2017 12:20 PM, Shirley Avishour wrote:
> Hi,
> I have an application over dpdk which is consisted of the following threads
> each running on a separate core:
> 1) rx thread which listens on in a poll mode for traffic
> 2) 2 packet processing threads (for load balancing)
> 3) kni thread (whi
Hi,
I have an application over dpdk which is consisted of the following threads
each running on a separate core:
1) rx thread which listens on in a poll mode for traffic
2) 2 packet processing threads (for load balancing)
3) kni thread (which also runs on a separate core).
the rx thread receives p
14 matches
Mail list logo
