This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH 05/10] Invalidate or shrink dcache when setting is changed.
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 18 Nov 2013 15:56:37 +0000
- Subject: Re: [PATCH 05/10] Invalidate or shrink dcache when setting is changed.
- Authentication-results: sourceware.org; auth=none
- References: <1383458049-20893-1-git-send-email-yao at codesourcery dot com> <1383458049-20893-6-git-send-email-yao at codesourcery dot com>
On 11/03/2013 05:54 AM, Yao Qi wrote:
> Nowadays, when cache size or line size is changed by command,
> 'target_dcache' is invalidated. It is too conservative. We can
> optimize in the following ways,
> - Don't have to invalidate dcache immediately after cache size or
> line size is changed. We can postpone the invalidation to the moment
> using 'target_dcache'.
> - Don't have to invalidate dcache if the cache size is changed. If
> cache size is changed to the value which is still greater than
> dcache's size, nothing should be done. If change to the value
> which is less than dcache's size, just evict cache lines.
> This is what this patch does.
Actually, my "My thoughts exactly." comment in the other patch was
originally directed at this patch. Do we really need this extra
complication? What's the use case that needs this?