; down from 1 to 1/n.
> Definitely, Writeboost isn't fit for a machine that needs reboot frequently
> (e.g. desktop).
>
> There is a way to reduce the init time. We can dump "what is the latest log
> written back"
> on the superblock. This can skip readings that aren't ess
() function. Please read if you
are
interested.
Thanks,
- Akira
On 12/13/14 3:45 PM, Jianjian Huo wrote:
If I understand it correctly, the whole idea indeed is very simple,
the consumer/provider and circular buffer model. use SSD as a circular
write buffer, write flush thread stores incoming
If I understand it correctly, the whole idea indeed is very simple,
the consumer/provider and circular buffer model. use SSD as a circular
write buffer, write flush thread stores incoming writes to this buffer
sequentially as provider, and writeback thread write those data logs
sequentially into
If I understand it correctly, the whole idea indeed is very simple,
the consumer/provider and circular buffer model. use SSD as a circular
write buffer, write flush thread stores incoming writes to this buffer
sequentially as provider, and writeback thread write those data logs
sequentially into
4 matches
Mail list logo
