[Click] Intel Core duo
Roman Chertov
rchertov at purdue.edu
Tue Jan 2 16:53:03 EST 2007
Qinghua(Kevin) Ye wrote:
> Hi, Roman,
>
> Have you compared the performance difference between one-thread, two-thread
I my particular configuration I have noticed improved performance with
more CPUs, when a few interfaces were used concurrently. I have used at
most 3 click threads as I wanted the remaining CPU for my user
application. It appears that speed up can be achieved when the
SaticThreadSched element is used; however, one must be careful when
assigning elements to avoid cases where frequent cache misses occur. I
think it would be useful to be able to assign an entire path to one CPU
to avoid caching issues.
something like this:
Poll0->DoSomething->ToDev0 CPU0
Poll1->DoSomething->ToDev1 CPU1
Roman
> and four-thread SMP click on the quad core Xeon? I have installed the SMP
> click on a dual core Xeon, but cannot achieve better performance with two
> threads. Thanks.
>
> Regards,
> Qinghua(Kevin) Ye
> ----- Original Message -----
> From: "Roman Chertov" <rchertov at purdue.edu>
> To: "william irvine" <wpirvine at gmail.com>
> Cc: <click at pdos.csail.mit.edu>
> Sent: Tuesday, January 02, 2007 7:55 AM
> Subject: Re: [Click] Intel Core duo
>
>
>> I am running SMP kernel and SMP click on a quad core Xeon machine. I've
>> had some crashes in the driver, but after I moved the click polling code
>> to the latest e1000 driver stability has improved. This could have been
>> because I have PCI-E dual port cards.
>>
>> william irvine wrote:
>>> A quick question as to the compatibility of click with the Intel Core
> duo
>>> processors? Have any of you guys had any insurmountable issues? Or
> shoulnd't
>>> i be worried and just take the plunge on a new machine with one of these
>>> chipsets?
>>>
>> _______________________________________________
>> click mailing list
>> click at amsterdam.lcs.mit.edu
>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>>
>
>
More information about the click
mailing list