This is mainly for Ben Booth who posted a request to SourceForge web site. SF site forwarded me his request a few days ago and I replied. But my mail doesn't appear on SF site, nor I did not get his answer. I am not sure my mail was delivered correctly. I tried re-sending to his mail address directly, but SF site bounced with saying "no such user."
So I post here with hoping he can see my reply. J. R. Okajima (first mail, his request posted) ------- Forwarded Message To: "Ticket 2" <2...@feature-requests.aufs.p.re.sf.net> From: "Ben Booth" <shy...@users.sf.net> Reply-To: "Ticket 2" <2...@feature-requests.aufs.p.re.sf.net> Subject: [aufs:feature-requests] #2 New COPY_UP policy based upon atime Message-ID: <53107b3d90954762c3aee0dd.feature-reque...@aufs.p.sourceforge.net> Date: Fri, 28 Feb 2014 12:04:14 +0000 This is a multi-part message in MIME format. - --===============5412569383833396465== Content-Type: multipart/alternative; boundary="===============5362711320803701537==" MIME-Version: 1.0 - --===============5362711320803701537== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit - --- ** [feature-requests:#2] New COPY_UP policy based upon atime** **Status:** open **Created:** Fri Feb 28, 2014 12:04 PM UTC by Ben Booth **Last Updated:** Fri Feb 28, 2014 12:04 PM UTC **Owner:** Junjiro Okajima New COPY_UP policy based upon atime. Should a file be accessed in a lower layer the file is copied up. Useful for situations where the bottom layers exist on network storage as FS performance would increase as the files are copied over to the local RW layer. - --- Sent from sourceforge.net because you indicated interest in <https://sourceforge.net/p/aufs/feature-requests/2/> To unsubscribe from further messages, please visit <https://sourceforge.net/auth/subscriptions/> - --===============5362711320803701537== MIME-Version: 1.0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit <div class="markdown_content"><hr /> <p><strong> <a class="alink" href="http://sourceforge.net/p/aufs/feature-requests/2/";>[feature-requests:#2]</a> New COPY_UP policy based upon atime</strong></p> <p><strong>Status:</strong> open<br /> <strong>Created:</strong> Fri Feb 28, 2014 12:04 PM UTC by Ben Booth<br /> <strong>Last Updated:</strong> Fri Feb 28, 2014 12:04 PM UTC<br /> <strong>Owner:</strong> Junjiro Okajima</p> <p>New COPY_UP policy based upon atime.</p> <p>Should a file be accessed in a lower layer the file is copied up. Useful for situations where the bottom layers exist on network storage as FS performance would increase as the files are copied over to the local RW layer.</p> <hr /> <p>Sent from sourceforge.net because you indicated interest in <a href="https://sourceforge.net/p/aufs/feature-requests/2/";>https://sourceforge.net/p/aufs/feature-requests/2/</a></p> <p>To unsubscribe from further messages, please visit <a href="https://sourceforge.net/auth/subscriptions/";>https://sourceforge.net/auth/subscriptions/</a></p></div> - --===============5362711320803701537==-- - --===============5412569383833396465==-- ------- End of Forwarded Message (second mail, my reply) From: sf...@users.sourceforge.net Subject: Re: [aufs:feature-requests] #2 New COPY_UP policy based upon atime To: "Ticket 2" <2...@feature-requests.aufs.p.re.sf.net> Date: Sat, 01 Mar 2014 15:05:59 +0900 Hello Ben, "Ben Booth": > New COPY_UP policy based upon atime. > > Should a file be accessed in a lower layer the file is copied up. Useful for > situations where the bottom layers exist on network storage as FS performance > would increase as the files are copied over to the local RW layer. Unfortunately I don't understand what you wrote enough. Do you want somehing like a "coo" option which was implemented in aufs1? Or will you explain "Should a file be accessed ... the file is copied up." more specifically? Because I don't think it a good idea to copy-up even for stat(2) systemcall. (quote from linux/Documentation/filesystems/aufs/design/99plan.tex) Copy-up on Open (coo=) ---------------------------------------------------------------------- By default the internal copy-up is executed when it is really necessary. It is not done when a file is opened for writing, but when write(2) is done. Users who have many (over 100) branches want to know and analyse when and what file is copied-up. To insert a new upper branch which contains such files only may improve the performance of aufs. Aufs1 implemented "coo=none | leaf | all" option. J. R. Okajima ------------------------------------------------------------------------------ Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis & security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
