<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:evnet="http://www.mscommunities.com/rssmodule/"><channel><title>Entries for Akaina</title><atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/niners/akaina/rss/default.aspx" /><image><url>http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.png</url><title>Entries for Akaina</title><link>http://channel9.msdn.com/Niners/akaina/</link></image><description>Entries, comments and threads posted by Akaina</description><link>http://channel9.msdn.com/Niners/akaina/</link><language>en-us</language><pubDate>Mon, 21 Jun 2004 13:26:06 GMT</pubDate><lastBuildDate>Mon, 21 Jun 2004 13:26:06 GMT</lastBuildDate><generator>EvNet (EvNet, Version=1.0.3192.39714, Culture=neutral, PublicKeyToken=null)</generator><item><title>Samba strict sync in &amp;quot;Get the Facts&amp;quot; [Samba strict sync in &amp;quot;Get the Facts&amp;quot;]</title><description>&lt;p&gt;Can someone who is familiar with both&amp;nbsp;SAMBA and Windows&amp;nbsp;Server 2003 file serving&amp;nbsp;please explain why Microsoft modified the default configuration of SAMBA for use in its "Get the Facts" campaign?&lt;br /&gt;&lt;br /&gt;The &lt;a href="http://download.microsoft.com/download/c/c/b/ccb52352-90e4-4260-8c8c-113571bf48f3/MSvsSamba.doc"&gt;MSvsSAMBA.doc&lt;/a&gt; says:&lt;br /&gt;&lt;br /&gt;&lt;em&gt;strict sync – When set to &lt;strong&gt;“yes”&lt;/strong&gt;, this share-level option instructs Samba to honor all requests to perform disk synchronization when requested to do so by a client. &lt;strong&gt;Default setting is “no”&lt;/strong&gt;.&lt;br /&gt;&lt;/em&gt;&lt;br /&gt;Could this be the culprit to show a "59%" performance difference between the two systems?&lt;/p&gt;&lt;p&gt;in reply to &lt;a href='http://channel9.msdn.com/forums/TechOff/10139-Samba-strict-sync-in-quotGet-the-Factsquot/'&gt;Samba strict sync in &amp;quot;Get the Facts&amp;quot;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://channel9.msdn.com/10139/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" /&gt;</description><comments>http://channel9.msdn.com/forums/TechOff/10139-Samba-strict-sync-in-quotGet-the-Factsquot/</comments><link>http://channel9.msdn.com/forums/TechOff/10139-Samba-strict-sync-in-quotGet-the-Factsquot/</link><pubDate>Mon, 21 Jun 2004 13:26:06 GMT</pubDate><guid isPermaLink="false">http://channel9.msdn.com/forums/TechOff/10139-Samba-strict-sync-in-quotGet-the-Factsquot/</guid><evnet:views>13723</evnet:views><evnet:viewtrackingurl>http://channel9.msdn.com/10139/WebViewBug.aspx?EVT=0</evnet:viewtrackingurl><evnet:previewtext>&lt;p&gt;Can someone who is familiar with both&amp;nbsp;SAMBA and Windows&amp;nbsp;Server 2003 file serving&amp;nbsp;please explain why Microsoft modified the default configuration of SAMBA for use in its "Get the Facts" campaign?&lt;br /&gt;&lt;br /&gt;The &lt;a href="http://download.microsoft.com/download/c/c/b/ccb52352-90e4-4260-8c8c-113571bf48f3/MSvsSamba.doc"&gt;MSvsSAMBA.doc&lt;/a&gt; says:&lt;br /&gt;&lt;br /&gt;&lt;em&gt;strict sync – When set to &lt;strong&gt;“yes”&lt;/strong&gt;, this share-level option instructs Samba to honor all requests to perform disk synchronization when requested to do so by a client. &lt;strong&gt;Default setting is “no”&lt;/strong&gt;.&lt;br /&gt;&lt;/em&gt;&lt;br /&gt;&lt;/p&gt;</evnet:previewtext><dc:creator>Akaina</dc:creator><slash:comments>15</slash:comments><wfw:commentRss>http://channel9.msdn.com/forums/TechOff/10139-Samba-strict-sync-in-quotGet-the-Factsquot/RSS/</wfw:commentRss><trackback:ping>http://channel9.msdn.com/10139/Trackback.aspx</trackback:ping></item><item><title>Inline routines [Inline routines]</title><description>&lt;p dir="ltr"&gt;Quick question,&lt;br /&gt;&lt;br /&gt;I'm not an expert with how .NET compiles, but I was wondering if there exists a feature anything like traditional C++ macros (#include, #whatever) whereby a function could be called with syntax not unlike a regular call, but allow&amp;nbsp;the function code&amp;nbsp;to be literally copied during compile time into an inline routine, thus removing repeated function calls.&lt;br /&gt;&lt;br /&gt;One&amp;nbsp;could re-use code and get the speed advantage&amp;nbsp;of hard-coding. Updates to the routine would not require modifying multiple instances of identicly hard-coded routines.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;e.g.&lt;br /&gt;&lt;br /&gt;inline function myInlineFunction&lt;br /&gt;{&lt;br /&gt;&amp;nbsp; //do lots of CPU intensive things here...&lt;br /&gt;&amp;nbsp; System.Console.Writeline("test function " + scopeVar + "\n");&lt;br /&gt;&amp;nbsp; System.Console.Writeline("test function " + scopeVar + "\n");&lt;br /&gt;&amp;nbsp; System.Console.Writeline("test function " + scopeVar + "\n");&lt;br /&gt;&amp;nbsp; System.Console.Writeline("test function " + scopeVar + "\n");&lt;br /&gt;&lt;br /&gt;}//end of myInlineFunction&lt;br /&gt;&lt;br /&gt;//meanwhile back at the ranch...&lt;br /&gt;&lt;br /&gt;Class1&lt;br /&gt;{&lt;br /&gt;&amp;nbsp; static void Main()&lt;br /&gt;&amp;nbsp; {&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;int&amp;nbsp;scopeVar = 1;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;ulong max_count = 99999999;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; System.out.writeline("Welcome to my speedy program\n\n");&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; for&amp;nbsp;(int i = 0; i &amp;lt; max_count; i++)&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; {&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; //normally a function call would be used 9999999 times&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;myInlineFunction;&amp;nbsp;&amp;nbsp;&amp;nbsp;//code is literally pasted here during compile-time&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; }//end of for&lt;br /&gt;&amp;nbsp; }//end of member Main&lt;br /&gt;}//end of Class1&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;This kind of routine would not be able to return values, or accept values, and would exist (have access to variables)&amp;nbsp;only within the scope&amp;nbsp;'this' of where it was called from.&lt;br /&gt;&lt;br /&gt;I could see this as a speed enhancement. Does it already exist? If this is a newb question, I appologize in advance.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;in reply to &lt;a href='http://channel9.msdn.com/forums/TechOff/4793-Inline-routines/'&gt;Inline routines&lt;/a&gt;&lt;/p&gt;&lt;img src="http://channel9.msdn.com/4793/WebViewBug.aspx?EVT=0" height="1" width="1" alt="" /&gt;</description><comments>http://channel9.msdn.com/forums/TechOff/4793-Inline-routines/</comments><link>http://channel9.msdn.com/forums/TechOff/4793-Inline-routines/</link><pubDate>Tue, 27 Apr 2004 14:36:16 GMT</pubDate><guid isPermaLink="false">http://channel9.msdn.com/forums/TechOff/4793-Inline-routines/</guid><evnet:views>4667</evnet:views><evnet:viewtrackingurl>http://channel9.msdn.com/4793/WebViewBug.aspx?EVT=0</evnet:viewtrackingurl><evnet:previewtext>&lt;p dir="ltr"&gt;Quick question,&lt;br /&gt;&lt;br /&gt;I'm not an expert with how .NET compiles, but I was wondering if there exists a feature anything like traditional C++ macros (#include, #whatever) whereby a function could be called with syntax not unlike a regular call, but allow&amp;nbsp;the function code&amp;nbsp;to be literally copied during compile time into an inline routine, thus removing repeated function calls.&lt;br /&gt;&lt;br /&gt;One&amp;nbsp;could re-use code and get the speed advantage&amp;nbsp;of hard-coding. Updates to the routine would not require modifying multiple instances of identicly hard-coded routines.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;e.g.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;</evnet:previewtext><dc:creator>Akaina</dc:creator><slash:comments>5</slash:comments><wfw:commentRss>http://channel9.msdn.com/forums/TechOff/4793-Inline-routines/RSS/</wfw:commentRss><trackback:ping>http://channel9.msdn.com/4793/Trackback.aspx</trackback:ping></item></channel></rss>