<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 21, 2017 at 3:26 AM, Raghavendra Gowdappa <span dir="ltr"><<a href="mailto:rgowdapp@redhat.com" target="_blank">rgowdapp@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
We've a bug [1], due to which read-ahead is completely disabled when the workload is read-only. One of the easy fix was to make read-ahead as an ancestor of open-behind in xlator graph (Currently its a descendant). A patch has been sent out by Rafi to do the same. As noted in one of the comments, one flip side of this solution is that small files (which are eligible to be cached by quick read) are cached twice - once each in read-ahead and quick-read - wasting up precious memory. However, there are no other simpler solutions for this issue. If you've concerns on the approach followed by [2] or have other suggestions please voice them out. Otherwise, I am planning to merge [2] for lack of better alternatives.<br></blockquote><div><br></div><div><br></div><div>Since the maximum size of files cached by quick-read is 64KB, can we have read-ahead kick in for offsets greater than 64KB?</div><div><br></div><div>Thanks,</div><div>Vijay</div></div></div></div>