On Thu, Oct 7, 2021 at 5:05 PM <andrii.nakryiko@xxxxxxxxx> wrote: > > From: Andrii Nakryiko <andrii@xxxxxxxxxx> > > Add support for having multiple .rodata and .data data sections ([0]). > .rodata/.data are supported like the usual, but now also > .rodata.<whatever> and .data.<whatever> are also supported. Each such > section will get its own backing BPF_MAP_TYPE_ARRAY, just like > .rodata and .data. > > Multiple .bss maps are not supported, as the whole '.bss' name is > confusing and might be deprecated soon, as well as user would need to > specify custom ELF section with SEC() attribute anyway, so might as well > stick to just .data.* and .rodata.* convention. > > User-visible map name for such new maps is going to be just their ELF > section names. When creating the map in the kernel, libbpf will still > try to prepend portion of object name. This feature is up for debate and > I'm open to dropping that for new maps entirely. > > [0] https://github.com/libbpf/libbpf/issues/274 > > Signed-off-by: Andrii Nakryiko <andrii@xxxxxxxxxx> Acked-by: Song Liu <songliubraving@xxxxxx>
