From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/23478] New: bpf: multi-key associative arrays
Date: Wed, 01 Aug 2018 19:04:00 -0000 [thread overview]
Message-ID: <bug-23478-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=23478
Bug ID: 23478
Summary: bpf: multi-key associative arrays
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bpf
Assignee: systemtap at sourceware dot org
Reporter: me at serhei dot io
Target Milestone: ---
From the 'language features' brainstorm:
# More complex structures: multi-key associative arrays
It's theoretically possible to have a large struct as the key to a hash map.
Thus, a key could literally be a structure with 2 (or more) embedded strings.
It seemed to work fine when I used a 128-byte map key size, so two 64-byte
string keys should be doable at the very least.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2018-08-01 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 19:04 me at serhei dot io [this message]
2019-05-28 13:51 ` [Bug bpf/23478] " wcohen at redhat dot com
2019-08-20 20:49 ` wcohen at redhat dot com
2021-08-30 15:21 ` me at serhei dot io
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=bug-23478-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).