[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] RE: SMP-g design notes


  • To: "Luck, Tony" <tony.luck@xxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Thu, 9 Mar 2006 09:05:17 +0800
  • Delivery-date: Thu, 09 Mar 2006 01:05:57 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZCqKZfyHU/3C/1SOWN7EU3LmnzJQAaYvPgAADOoVA=
  • Thread-topic: [Xen-ia64-devel] RE: SMP-g design notes

>From: Luck,Tony
>Sent: 2006年3月9日 8:55
>To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: [Xen-ia64-devel] RE: SMP-g design notes
>
>> Because it is design time, here are some note about my SMP-g work.
>> The current patch is very small.  I tried only to bring-up SMP-g ASAP to
>catch
>> more SMP bugs.  Also I tried to minimize Linux kernel changes.
>                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
><philosophy>
>In almost all design decisions you need to make tradeoffs ... I don't
>think that "minimizing Linux kernel changes" should be very high up
>the list of priorities when making a choice.  Correctness is always
>at the top, meeting requirements, complexity, maintainability and
>performance should be close behind.  Not disturbing the existing source
>base too much is much further down the list (which is not to be
>interpreted as "Tony wants to see huge patches that change everything"
>... when they come, Tony wants to see intelligent patches that do the
>right things in the right layer rather than a minimal patch in one
>layer, and an ugly mess to compensate in another layer).
></philosophy>
>
>-Tony
>

Totally agree. :-P

Thanks,
Kevin

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.