All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: hi3766691@gmail.com, Hillf Danton <dhillf@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Zhouping Liu <zliu@redhat.com>
Subject: Re: Kernel panic - not syncing: Attempted to kill the idle task!
Date: Tue, 12 Jun 2012 13:08:26 +0200	[thread overview]
Message-ID: <1339499306.31548.75.camel@twins> (raw)
In-Reply-To: <1339496836.31548.68.camel@twins>

On Tue, 2012-06-12 at 12:27 +0200, Peter Zijlstra wrote:
> On Tue, 2012-06-12 at 13:20 +0300, Linus Torvalds wrote:
> > Peter, you are very fundamentally wrong if you think the distance
> > array has to be symmetric. That is fundamentally not true for many
> > typologies.
> > 
> > The trivial example of a non symmetric case is just a simple
> > unidirectional ring. The distance from n to n+1 is just one, but the
> > distance from n+1 to n is n-1 hops.
> > 
> > So don't try to say that distances have to be symmetric. That's just
> > garbage. 
> 
> Sure, I realize this, but the 17,18 thing isn't a ring. It looks like
> something that should be symmetric but isn't.

Not a unidirectional one that is.. I played around a bit more and found
a shape that isn't too odd:


                  2
                /   \
              0       5
             /      /  \
            1 --- / --- 3
             \  /      /
              4       6
                \   /
                  7 


I would've crossed 0<->6 instead of 1<->3 so the 2/3 connected nodes are
spread better, but what do I know.

The only really odd thing is the numbering, which is what threw me.

But yeah, the possibility of uni-directional rings makes detecting
obvious crack tables harder, which is why I haven't got it -- yet.

  reply	other threads:[~2012-06-12 11:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 17:13 Kernel panic - not syncing: Attempted to kill the idle task! ZhouPing Liu
2012-06-08 18:46 ` Peter Zijlstra
2012-06-09  1:38   ` Zhouping Liu
2012-06-11 13:27     ` Peter Zijlstra
2012-06-11 13:51       ` Borislav Petkov
2012-06-12  3:54       ` Zhouping Liu
2012-06-12  6:39         ` Zhouping Liu
2012-06-12  8:49         ` Peter Zijlstra
     [not found]           ` <CA+55aFw=akW7B+vRkQRMojnP6_b1YXdKpNEjQ2EyBHcTe2_XLw@mail.gmail.com>
2012-06-12 10:27             ` Peter Zijlstra
2012-06-12 11:08               ` Peter Zijlstra [this message]
2012-06-12 16:45             ` Peter Zijlstra
     [not found] <1158989060.155090.1306033067946.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2011-05-22  3:37 ` Qiannan Cui
2011-05-22 23:43   ` Minchan Kim
2011-05-23 10:08     ` Qiannan Cui
2011-05-23 15:46       ` Minchan Kim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1339499306.31548.75.camel@twins \
    --to=peterz@infradead.org \
    --cc=aarcange@redhat.com \
    --cc=dhillf@gmail.com \
    --cc=hi3766691@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=zliu@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.