<br><br><div class="gmail_quote">On Wed, Dec 22, 2010 at 6:53 PM, Satish Balay <span dir="ltr"><<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Wed, 22 Dec 2010, Yongjun Chen wrote:<br>
<br>
> On Wed, Dec 22, 2010 at 6:32 PM, Satish Balay <<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>> wrote:<br>
><br>
</div><div class="im">> > Thanks a lot, Satish. It is much clear now. But for the choice of the two,<br>
> the program dmidecode does not show this information. Do you know any way to<br>
> get it?<br>
<br>
</div>why do you expect dmidecode to show that?<br>
<br>
You'll have to look for the CPU/chipset hardware documentation - and<br>
look at the details - and sometimes they mention these details..<br>
<font color="#888888"><br>
Satish<br>
</font></blockquote></div><br><br>Thanks, Satish. Yes, I need to check it.<br>Just now I re-configured PETSC with the option --with-device=ch3:nemsis. The results are almost the same as --with-device=ch3:sock. As can be seen in the attachment.<br>
I hope the matrix partitioning - reordering algorithm would have some positive effects. <br><br>