>> Almost ;-) memory pressure doesn't need to care about how long a
>> buffer has been dirty, that's kupdate's job. kupdate doesn't care if
>> the buffer it is writing is a good candidate for freeing, that's taken
>> care of elsewhere. The two never need to talk (aside from
> My point is, they should talk, in fact they should be the same function.
> It's never right for bdflush to submit younger buffers when there are
> dirty buffers whose flush time has already passed.
Grin, we're talking in circles. My point is that by having two threads,
bdflush is allowed to skip over older buffers in favor of younger ones
because somebody else is responsible for writing the older ones out.
Take away the kupdate thread and bdflush must write the older buffer. I
believe this limits optimizations, unless kswapd is changed to handle all
memory pressure flushes.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/