Re: [PATCH 17/32] read-cache: split-index mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Duy Nguyen <pclouds@xxxxxxxxx> writes:

> when no entry is reused). I kinda hope to avoid that.

I see.

> Speaking about
> reusing cache_entry, we won't be able to share cache_entry because
> when it's freed in replace_index_entry, or remove_index_entry_at in
> the main index, we need to locate the same entry in the shared index
> as well and remove that stale pointer. Without sharing, we nearly
> double memory usage from the beginning.

Yeah, the point being to have most of the entries come from the base
one, it is expected the real one and the saved base one will be
mostly the same, so sharing is really necessary.

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]