<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for portrix systems</title>
	<atom:link href="http://portrix-systems.de/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://portrix-systems.de</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 11:12:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on OVDC 1.2 for iPad released by Create exceptions for non-smartcard sun ray logins &#124; portrix systems</title>
		<link>http://portrix-systems.de/blog/brost/ovdc-1-2-for-ipad-released/comment-page-1/#comment-3484</link>
		<dc:creator>Create exceptions for non-smartcard sun ray logins &#124; portrix systems</dc:creator>
		<pubDate>Wed, 22 May 2013 11:12:02 +0000</pubDate>
		<guid isPermaLink="false">http://portrix-systems.de/?p=1601#comment-3484</guid>
		<description><![CDATA[[...] the introduction of OVDC softclients (either for PC or Mac or tablets) has made this a bit more complicated. You can of course use a USB cardreader with your laptop but I [...]]]></description>
		<content:encoded><![CDATA[<p>[...] the introduction of OVDC softclients (either for PC or Mac or tablets) has made this a bit more complicated. You can of course use a USB cardreader with your laptop but I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ZFS migration using incremental send/receive by Bjoern Rost</title>
		<link>http://portrix-systems.de/blog/brost/zfs-migration-using-incremental-sendreceive/comment-page-1/#comment-3473</link>
		<dc:creator>Bjoern Rost</dc:creator>
		<pubDate>Thu, 16 May 2013 16:09:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.portrix-systems.de/?p=860#comment-3473</guid>
		<description><![CDATA[Thanks for mentioning that. zp04 was another pool that I migrated on the same box but I guess it is confusing to have it in the example so I modified it.]]></description>
		<content:encoded><![CDATA[<p>Thanks for mentioning that. zp04 was another pool that I migrated on the same box but I guess it is confusing to have it in the example so I modified it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on ZFS migration using incremental send/receive by Olaf Marzocchi</title>
		<link>http://portrix-systems.de/blog/brost/zfs-migration-using-incremental-sendreceive/comment-page-1/#comment-3472</link>
		<dc:creator>Olaf Marzocchi</dc:creator>
		<pubDate>Thu, 16 May 2013 16:02:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.portrix-systems.de/?p=860#comment-3472</guid>
		<description><![CDATA[I think you introduced zp04 without explaining where it is coming from. A typo maybe?]]></description>
		<content:encoded><![CDATA[<p>I think you introduced zp04 without explaining where it is coming from. A typo maybe?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on using PCIe direct IO with ldoms by Bjoern Rost</title>
		<link>http://portrix-systems.de/blog/brost/using-direct-io-with-ldoms/comment-page-1/#comment-3471</link>
		<dc:creator>Bjoern Rost</dc:creator>
		<pubDate>Thu, 16 May 2013 08:57:47 +0000</pubDate>
		<guid isPermaLink="false">http://portrix-systems.de/?p=1479#comment-3471</guid>
		<description><![CDATA[ta, I created a little table with information on the PCIe slots: http://portrix-systems.de/blog/brost/t4-2-pcie-physical-slot-layout/]]></description>
		<content:encoded><![CDATA[<p>ta, I created a little table with information on the PCIe slots: <a href="http://portrix-systems.de/blog/brost/t4-2-pcie-physical-slot-layout/" rel="nofollow">http://portrix-systems.de/blog/brost/t4-2-pcie-physical-slot-layout/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on using PCIe direct IO with ldoms by T4-2 PCIe physical slot layout &#124; portrix systems</title>
		<link>http://portrix-systems.de/blog/brost/using-direct-io-with-ldoms/comment-page-1/#comment-3470</link>
		<dc:creator>T4-2 PCIe physical slot layout &#124; portrix systems</dc:creator>
		<pubDate>Thu, 16 May 2013 08:51:42 +0000</pubDate>
		<guid isPermaLink="false">http://portrix-systems.de/?p=1479#comment-3470</guid>
		<description><![CDATA[[...] is in response to a question I received in another blog post concerning the mapping of physical PCIe slots to the two controllers (and subsequentially CPUs). [...]]]></description>
		<content:encoded><![CDATA[<p>[...] is in response to a question I received in another blog post concerning the mapping of physical PCIe slots to the two controllers (and subsequentially CPUs). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on using PCIe direct IO with ldoms by ta</title>
		<link>http://portrix-systems.de/blog/brost/using-direct-io-with-ldoms/comment-page-1/#comment-3453</link>
		<dc:creator>ta</dc:creator>
		<pubDate>Sun, 12 May 2013 12:46:07 +0000</pubDate>
		<guid isPermaLink="false">http://portrix-systems.de/?p=1479#comment-3453</guid>
		<description><![CDATA[Hi,
nice work.
i have a T4-2. as you said there are 2 pcie buses.
when i divide the both pcie buses into 2 domain.
like pcie0 to control domain and pcie1 to alternate io domain.
i just need to know that which pice slots will be connected to pice bus0 and which slots will be connected to pcie bus1??]]></description>
		<content:encoded><![CDATA[<p>Hi,<br />
nice work.<br />
i have a T4-2. as you said there are 2 pcie buses.<br />
when i divide the both pcie buses into 2 domain.<br />
like pcie0 to control domain and pcie1 to alternate io domain.<br />
i just need to know that which pice slots will be connected to pice bus0 and which slots will be connected to pcie bus1??</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on IP over the clouds by IP on a boat &#124; portrix systems</title>
		<link>http://portrix-systems.de/blog/brost/ip-over-the-clouds/comment-page-1/#comment-3260</link>
		<dc:creator>IP on a boat &#124; portrix systems</dc:creator>
		<pubDate>Fri, 19 Apr 2013 15:25:01 +0000</pubDate>
		<guid isPermaLink="false">http://portrix-systems.de/?p=1244#comment-3260</guid>
		<description><![CDATA[[...] have previously written about my experience with wifi on a plane, today I am at the OUGN conference on a cruiseship between Oslo an Kiel which offers a satellite [...]]]></description>
		<content:encoded><![CDATA[<p>[...] have previously written about my experience with wifi on a plane, today I am at the OUGN conference on a cruiseship between Oslo an Kiel which offers a satellite [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on using PCIe direct IO with ldoms by Bjoern Rost</title>
		<link>http://portrix-systems.de/blog/brost/using-direct-io-with-ldoms/comment-page-1/#comment-3120</link>
		<dc:creator>Bjoern Rost</dc:creator>
		<pubDate>Mon, 15 Apr 2013 16:34:59 +0000</pubDate>
		<guid isPermaLink="false">http://portrix-systems.de/?p=1479#comment-3120</guid>
		<description><![CDATA[yes, in this example, I only assigned a single endpoint device to my ldom. One could also assign a whole PCIe bus (that feature has been included for a while) but I did not want to do this in this case. The primary ldom boots from disks on an HBA that is also on one of those busses and I also preferred to virtualize the NICs in the primary domain.]]></description>
		<content:encoded><![CDATA[<p>yes, in this example, I only assigned a single endpoint device to my ldom. One could also assign a whole PCIe bus (that feature has been included for a while) but I did not want to do this in this case. The primary ldom boots from disks on an HBA that is also on one of those busses and I also preferred to virtualize the NICs in the primary domain.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on using PCIe direct IO with ldoms by laotsao</title>
		<link>http://portrix-systems.de/blog/brost/using-direct-io-with-ldoms/comment-page-1/#comment-3091</link>
		<dc:creator>laotsao</dc:creator>
		<pubDate>Mon, 15 Apr 2013 08:56:27 +0000</pubDate>
		<guid isPermaLink="false">http://portrix-systems.de/?p=1479#comment-3091</guid>
		<description><![CDATA[hi
IMHO, younuse the pcie bus too lossely
in your example, you assign pcie slots(end point) to the io-domain , not the pcie bus]]></description>
		<content:encoded><![CDATA[<p>hi<br />
IMHO, younuse the pcie bus too lossely<br />
in your example, you assign pcie slots(end point) to the io-domain , not the pcie bus</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on favourite Oracle 12c database features of OpenWorld Bloggers by Seth</title>
		<link>http://portrix-systems.de/blog/brost/favourite-oracle-12c-database-features-of-openworld-bloggers/comment-page-1/#comment-3034</link>
		<dc:creator>Seth</dc:creator>
		<pubDate>Sun, 14 Apr 2013 17:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://portrix-systems.de/?p=1285#comment-3034</guid>
		<description><![CDATA[Pluggable and Data Guard Far Sync are my most preferred picks of the lot. Orable 12c Database features have opened up a world of opportunity to bloggers.]]></description>
		<content:encoded><![CDATA[<p>Pluggable and Data Guard Far Sync are my most preferred picks of the lot. Orable 12c Database features have opened up a world of opportunity to bloggers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Flex Everything in Oracle RAC 12c by favourite Oracle 12c database features of OpenWorld Bloggers &#124; portrix systems</title>
		<link>http://portrix-systems.de/blog/brost/flex-everything-in-oracle-rac-12c/comment-page-1/#comment-3020</link>
		<dc:creator>favourite Oracle 12c database features of OpenWorld Bloggers &#124; portrix systems</dc:creator>
		<pubDate>Sun, 14 Apr 2013 13:13:49 +0000</pubDate>
		<guid isPermaLink="false">http://portrix-systems.de/?p=1802#comment-3020</guid>
		<description><![CDATA[[...] Jason Arneil (@jarneil) loves Cluster ASM for the fact that it will be possible to have multiple ASM instances running on the same system. The concern is that when you consolidate databases they all become dependant on only one ASM instance. And if that one has issues, all databases on the system will get taken down with it. Apparently, the problem is big enough that people were already fiddling with this in 11g and managed to start multiple ASMs even though it is not supported. (update 2013/04/14: blogged about it) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Jason Arneil (@jarneil) loves Cluster ASM for the fact that it will be possible to have multiple ASM instances running on the same system. The concern is that when you consolidate databases they all become dependant on only one ASM instance. And if that one has issues, all databases on the system will get taken down with it. Apparently, the problem is big enough that people were already fiddling with this in 11g and managed to start multiple ASMs even though it is not supported. (update 2013/04/14: blogged about it) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Flex Everything in Oracle RAC 12c by Bjoern Rost</title>
		<link>http://portrix-systems.de/blog/brost/flex-everything-in-oracle-rac-12c/comment-page-1/#comment-3017</link>
		<dc:creator>Bjoern Rost</dc:creator>
		<pubDate>Sun, 14 Apr 2013 12:44:27 +0000</pubDate>
		<guid isPermaLink="false">http://portrix-systems.de/?p=1802#comment-3017</guid>
		<description><![CDATA[Hi Peter,

exactly. That failover is the whole point of flex asm. So it increases availability in cases of crashes (or planned outages) of ASM instances.

cheers
Björn]]></description>
		<content:encoded><![CDATA[<p>Hi Peter,</p>
<p>exactly. That failover is the whole point of flex asm. So it increases availability in cases of crashes (or planned outages) of ASM instances.</p>
<p>cheers<br />
Björn</p>
]]></content:encoded>
	</item>
</channel>
</rss>
