lkml.org 
[lkml]   [2004]   [Feb]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Bugme-new] [Bug 2019] New: Bug from the mm subsystem involving X (fwd)
>> 1 --- 2
>>| |
>>| |
>>| |
>> 3 --- 4
>>
>> then domains of (1,2,3) (2,3,4) (1,3,4) (1 2 4), with a view to restricting
>> the "double hop" traffic as much as possible. But I'm not sure the domains
>> code copes with multiple overlapping domains - Nick?
>>
>>
>
> Yes it can do ring topologies like this. I'm pretty sure it can do
> just about any sort of topology although this is one that I sat
> down and drew when designing it.
>
> You can technically restrict a double hop, but after you move, say,
> clockwise once, you might just as easily be moved clockwise again.
> The only way to restrict this is with some kind of home domain thing.

Well, this doesn't ban it, but requiring the double migrate will curtail
it somewhat, which is better than nothing.

M.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:00    [W:0.267 / U:0.584 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site