Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Jacob Potter <jdpotter@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Rewrite data cache to use splay tree
Date: Fri, 21 Aug 2009 03:04:00 -0000	[thread overview]
Message-ID: <e394668d0908201551x7bac1bdo3e81351ae32d5d77@mail.gmail.com> (raw)
In-Reply-To: <e394668d0908201533y3086ced8o177c69c27f4b282b@mail.gmail.com>

On Thu, Aug 20, 2009 at 3:33 PM, Doug Evans<dje@google.com> wrote:
> Hi.
>
> I checked in a sligntly modified version of this patch.
> The actual stack caching patch is still todo.
>
> 2009-08-20  Jacob Potter  <jdpotter@google.com>
>
>        Replace dcache with splay tree.
>        Remove partially implemented writeback support.
>        * dcache.c: Include splay-tree.h.
>        (LINE_SIZE_POWER): Change from 5 to 6.
>        (DCACHE_SIZE): Change from 64 to 4096.
>        (ENTRY_INVALID, ENTRY_VALID, ENTRY_DIRTY): Delete.
>        (state_chars): Delete.
>        (struct dcache_block): Clean up; remove state and anydirty fields.
>        (struct dcache_struct): Redefine as a splay tree and linked list.
>        (last_cache): Make static.
>        (dcache_invalidate, dcache_hit): Rewrite for new cache structure.
>        (dcache_read_line, dcache_alloc): Rewrite for new cache structure.
>        (dcache_write_line): Delete.
>        (dcache_writeback): Delete.
>        (dcache_peek_byte): Clean up; remove "invalid" state check.
>        (dcache_poke_byte): Rewrite for new cache structure; clarify comment.
>        (dcache_splay_tree_compare): New function.
>        (dcache_init, dcache_free): Rewrite for new cache structure.
>        (dcache_xfer_memory): Rewrite for new write-through cache structure.
>        (dcache_print_line): New function.
>        (dcache_info): Rewrite for new cache structure.
>        (_initialize_dcache): Update "info dcache" help text.
>        * dcache.h (dcache_xfer_memory): Update declaration.
>        * target.c (memory_xfer_partial): Update calls to dcache_xfer_memory.
>

Blech.  There's one more bit of cleanup that needed to be done.  It
was on my mental list, and then got dropped.  One can't use %lx to
print CORE_ADDRs.  Fixing pronto.


      reply	other threads:[~2009-08-20 22:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 21:25 Jacob Potter
2009-08-20 22:51 ` Doug Evans
2009-08-21  3:04   ` Doug Evans [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e394668d0908201551x7bac1bdo3e81351ae32d5d77@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jdpotter@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox