On 12/12/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
> Now in this case, you tested the acceptsize knob, found that if you
> turn it up there's an improvement, and if you leave it free to float
> all the way up it hurts nothing. You discovered that there's one
> correct setting: on. Or at least, you have no evidence to suggest when
> you ever would turn it down. Well done! Job sorted.
OK
> So, what if readahead > bufsize, what does that mean? When we
> read-ahead, we read directly into the buffer. If the buffer is
> read-ahead sized, no point reading in smaller than neccessary bufsize
> chunks.
> What if readahead < bufsize? Does it mean the buffer will never be
> fully filled? What kind of sense does that make.
>
> Reading nsd/driver.c, it's really not obvious what's going on.
I will see into that, readahead could be unnesassary
Well, the concept is necessary. We added it ourselves after discussing
it a whole lot!
But there are some weird interactions going on in that section of
code. The intent is not clear at all.
