|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel][Pv-ops][PATCH 3/3 v3] Netback: Use Kernel thread to repl
To: |
Dulloor <dulloor@xxxxxxxxx> |
Subject: |
RE: [Xen-devel][Pv-ops][PATCH 3/3 v3] Netback: Use Kernel thread to replace the tasklet. |
From: |
"Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx> |
Date: |
Wed, 5 May 2010 10:27:10 +0800 |
Accept-language: |
en-US |
Acceptlanguage: |
en-US |
Cc: |
Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jeremy, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Beulich <JBeulich@xxxxxxxxxx>, Jan, Steven Smith <steven.smith@xxxxxxxxxx> |
Delivery-date: |
Tue, 04 May 2010 19:29:48 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<q2u940bcfd21005041215l85a125cfo92c8a7bbf9f48575@xxxxxxxxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<D5AB6E638E5A3E4B8F4406B113A5A19A1D94B449@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <q2u940bcfd21005041215l85a125cfo92c8a7bbf9f48575@xxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
Thread-index: |
Acrrvh9+mi8hDubqT3+mwvZNSl/2BQAO88zg |
Thread-topic: |
[Xen-devel][Pv-ops][PATCH 3/3 v3] Netback: Use Kernel thread to replace the tasklet. |
Dulloor wrote:
> On Mon, May 3, 2010 at 6:52 PM, Xu, Dongxiao <dongxiao.xu@xxxxxxxxx>
> wrote:
>> Netback: Use Kernel thread to replace the tasklet.
>>
>> Kernel thread has more control over QoS, and could improve dom0's
>> userspace responseness. This option is defaultly off currently.
>
> Why not use just kthreads ?
Actually according to our previous testing, kthreads will cost more cpu
cycle than tasklet under certain workload, due to the frequent context
switch. But kthread could achieve more control over QoS. Therefore we
offer this option.
>
> Also, the multiple checks for MODPARM_kthread could be avoided using
> an inline function : schedule_netback_thread
Thanks for the suggestion.
Best Regards,
-- Dongxiao
>
>>
>> Signed-off-by: Dongxiao Xu <dongxiao.xu@xxxxxxxxx>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>>
>>
>
> -dulloor
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|