Changes between Initial Version and Version 1 of Ticket #25009


Ignore:
Timestamp:
Jan 24, 2018, 7:06:34 PM (14 months ago)
Author:
nickm
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #25009

    • Property Status changed from new to accepted
    • Property Owner set to nickm
    • Property Summary changed from Can outbuf_table_add be made to allocate less? to I think KIST can use hash tables much less.
  • Ticket #25009 – Description

    initial v1  
    1 It shows up in our malloc profile (#23777), where I hadn't been expecting to see it.
     1Originally, I observed that outbuf_table_add shows up in our malloc profile (#23777), where I hadn't been expecting to see it.
     2
     3After a little more thinking, I'm wondering why we have outbuf_table and socket_table at all:
     4
     5The contents of socket_table_ent could become a member of channel_t, and save us a hashtable lookup there.
     6
     7The outbuf_table could become a smartlist with a corresponding index pointer in channel_t, since we're basically using it as an unordered set.