content large_stringlengths 3 20.5k | url large_stringlengths 53 192 ⌀ | branch large_stringclasses 4
values | source large_stringclasses 51
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
-march=bpf -filetype=obj -o xdp-example.o The generated LLVM IR can also be dumped in human readable format through: .. code-block:: shell-session $ clang -O2 -Wall -emit-llvm -S -c xdp-example.c -o - LLVM can attach debug information such as the description of used data types in the program to the generated BPF object... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.007170765660703182,
0.026850998401641846,
-0.05731887370347977,
-0.009888040833175182,
0.06836586445569992,
-0.032777734100818634,
-0.035256750881671906,
0.060633305460214615,
-0.05976252630352974,
-0.022686198353767395,
0.03556274250149727,
-0.0872567668557167,
-0.050099506974220276,
-0... | 0.120959 |
-Xclang -target-feature -Xclang +dwarfris -c xdp-example.c -o xdp-example.o After successful compilation ``pahole`` can be used to properly dump structures of the BPF program based on the DWARF information: .. code-block:: shell-session $ pahole xdp-example.o struct xdp\_md { \_\_u32 data; /\* 0 4 \*/ \_\_u32 data\_end... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.016160547733306885,
0.052912354469299316,
-0.021039435639977455,
-0.053227588534355164,
0.022019580006599426,
-0.07539112120866776,
-0.0013696664245799184,
0.007772382814437151,
-0.0806681215763092,
0.013957097195088863,
0.04222341626882553,
-0.1289457380771637,
-0.033989060670137405,
-... | 0.017625 |
may turn a C switch statement into a switch table lookup and jump operation. Since the switch table is placed in the global read-only section, the bpf program will fail to load. The bpf target does not support switch table optimization. The clang option ``-fno-jump-tables`` can be used to disable switch table generatio... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.056781105697155,
-0.04277042672038078,
-0.042720627039670944,
-0.04270637035369873,
-0.035375144332647324,
-0.01145221572369337,
-0.06428810954093933,
0.06536007672548294,
-0.08621430397033691,
-0.002271727193146944,
-0.005636227782815695,
-0.06725353747606277,
-0.11113078892230988,
-0.0... | 0.023532 |
available.\*\* Shared libraries, etc cannot be used with BPF. However, common library code used in BPF programs can be placed into header files and included in the main programs. For example, Cilium makes heavy use of it (see ``bpf/lib/``). However, this still allows for including header files, for example, from the ke... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.02567298896610737,
-0.016845786944031715,
-0.04976774379611015,
-0.05453949794173241,
0.03565047308802605,
0.02064097858965397,
-0.040983591228723526,
0.005320737138390541,
-0.014823265373706818,
-0.07871368527412415,
-0.018797507509589195,
-0.015246926806867123,
-0.020024990662932396,
... | 0.044391 |
map\_lookup\_elem(&acc\_map, &dir); if (bytes) lock\_xadd(bytes, skb->len); return TC\_ACT\_OK; } \_\_section("ingress") int tc\_ingress(struct \_\_sk\_buff \*skb) { return account\_data(skb, 0); } \_\_section("egress") int tc\_egress(struct \_\_sk\_buff \*skb) { return account\_data(skb, 1); } char \_\_license[] \_\_s... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.059353820979595184,
0.03380408510565758,
-0.09937706589698792,
-0.09557494521141052,
0.035636816173791885,
-0.05037657171487808,
0.08851959556341171,
0.035667575895786285,
-0.014695808291435242,
-0.04928301274776459,
0.06127781793475151,
-0.03762916103005409,
0.03812767192721367,
-0.124... | 0.123018 |
Thus, upon loading of the ``ingress`` program, tc will find that no such map exists in the BPF file system and creates a new one. On success, the map will also be pinned, so that when the ``egress`` program is loaded through tc, it will find that such map already exists in the BPF file system and will reuse that for th... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.060281816869974136,
0.06263552606105804,
-0.04121962562203407,
0.004467464517802,
-0.010469204746186733,
-0.014429762959480286,
0.02498302049934864,
0.045178238302469254,
0.04396925866603851,
0.0023610612843185663,
0.03997573256492615,
-0.05628286674618721,
0.012514605186879635,
-0.0875... | 0.148698 |
# define printk(fmt, ...) \ ({ \ char \_\_\_\_fmt[] = fmt; \ trace\_printk(\_\_\_\_fmt, sizeof(\_\_\_\_fmt), ##\_\_VA\_ARGS\_\_); \ }) #endif The program can then use the macro naturally like ``printk("skb len:%u\n", skb->len);``. The output will then be written to the trace pipe. ``tc exec bpf dbg`` can be used to ret... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.005391231272369623,
0.02965562604367733,
-0.10113193094730377,
0.003444444388151169,
-0.033205680549144745,
-0.011552331037819386,
0.11233920603990555,
0.10227780789136887,
-0.041444625705480576,
-0.06918370723724365,
-0.010504786856472492,
-0.05477265268564224,
0.024193590506911278,
-0.... | 0.095023 |
Tail calls provide the flexibility to atomically alter program behavior during runtime by jumping from one BPF program into another. In order to select the next program, tail calls make use of program array maps (``BPF\_MAP\_TYPE\_PROG\_ARRAY``), and pass the map as well as the index to the next program to jump to. The... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.0057335044257342815,
-0.02145780809223652,
0.0021608448587358,
-0.035174380987882614,
-0.028277074918150902,
-0.053249482065439224,
0.04904378950595856,
0.06016019731760025,
0.06699023395776749,
-0.055030014365911484,
-0.03033277578651905,
0.019942117854952812,
-0.06503906100988388,
-0.0... | 0.215706 |
id and the entry within that map: .. code-block:: shell-session $ llvm-objdump -S --no-show-raw-insn prog\_array.o | less prog\_array.o: file format ELF64-BPF Disassembly of section 1/0: looper: 0: r6 = r1 1: r2 = \*(u32 \*)(r6 + 48) 2: r1 = r2 3: r1 += 1 4: \*(u32 \*)(r6 + 48) = r1 5: r1 = 0 ll 7: call -1 8: r1 = r6 9... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.010606946423649788,
0.11496998369693756,
-0.08931883424520493,
-0.06384190171957016,
0.013274626806378365,
-0.07042291015386581,
0.04757773503661156,
0.06582564860582352,
-0.011804888024926186,
-0.00496467761695385,
0.02197931334376335,
-0.05553727224469185,
-0.05511784180998802,
-0.0674... | 0.144799 |
this, the size of struct may often grow larger than expected. .. code-block:: c struct called\_info { u64 start; // 8-byte u64 end; // 8-byte u32 sector; // 4-byte }; // size of 20-byte ? printf("size of %d-byte\n", sizeof(struct called\_info)); // size of 24-byte // Actual compiled composition of struct called\_info /... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.0022732792422175407,
0.07059206068515778,
-0.04548213258385658,
-0.02827330119907856,
-0.016588909551501274,
-0.09003211557865143,
-0.012707187794148922,
0.13087819516658783,
-0.03828613460063934,
-0.04802035912871361,
0.05536763742566109,
-0.006197284907102585,
-0.0496649332344532,
-0.... | 0.050176 |
example, the compiler will generate less optimized code. Since we've removed the padding, processors will conduct unaligned access to the structure and this might lead to performance degradation. And also, unaligned access might get rejected by verifier on some architectures. However, there is a way to avoid downsides ... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.02214425429701805,
0.07113786041736603,
-0.06684939563274384,
-0.019937101751565933,
0.02165617048740387,
-0.12147579342126846,
-0.018586495891213417,
0.07691846042871475,
-0.016097502782940865,
-0.06253709644079208,
0.05174186825752258,
0.010238053277134895,
-0.03727944567799568,
-0.01... | 0.083412 |
and debugging. All BPF program types supported by iproute2 share the same BPF loader logic due to having a common loader back end implemented as a library (``lib/bpf.c`` in iproute2 source tree). The previous section on LLVM also covered some iproute2 parts related to writing BPF C programs, and later sections in this ... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.011674484238028526,
-0.04664919897913933,
0.0275974553078413,
-0.028042569756507874,
0.03806048259139061,
-0.04021738842129707,
-0.01793813519179821,
0.11126627773046494,
-0.030574981123209,
-0.027608349919319153,
-0.01155942864716053,
-0.021322118118405342,
-0.07199453562498093,
-0.102... | 0.026775 |
ensure received packet are set up linearly within a single page for BPF to read and write into. However, once completed, then most drivers only need to perform an atomic replacement of the program itself when a BPF program is requested to be swapped. In total, XDP supports three operation modes which iproute2 implement... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.017606226727366447,
-0.04019274190068245,
0.050475604832172394,
-0.07560788840055466,
0.02898424118757248,
-0.06345298886299133,
0.046768687665462494,
0.0570162869989872,
-0.04743102192878723,
-0.02676997147500515,
0.05941176041960716,
-0.000037345413147704676,
-0.02653501369059086,
-0.0... | 0.074211 |
on em1 0: (b7) r0 = 1 1: (95) exit # ip link set dev em1 xdpgeneric off And last but not least offloaded XDP, where we additionally dump program information via bpftool for retrieving general metadata: .. code-block:: shell-session # ip -force link set dev em1 xdpoffload obj prog.o # ip link show [...] 6: em1: mtu 1500... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.026062065735459328,
0.02026973105967045,
-0.00362854590639472,
-0.052312783896923065,
0.08590630441904068,
-0.07125838845968246,
0.054545484483242035,
0.028174804523587227,
-0.011285477317869663,
-0.014702253974974155,
0.08535543829202652,
-0.06480243057012558,
0.012704377062618732,
-0.... | 0.03746 |
is processed lockless from ``ingress`` and ``egress`` direction and can also be attached to virtual, queue-less devices such as ``veth`` devices connecting containers. Next to the hook, the ``tc filter`` command selects ``bpf`` to be used in ``da`` (direct-action) mode. ``da`` mode is recommended and should always be s... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.04985075816512108,
0.010661851614713669,
-0.035008665174245834,
-0.06093916296958923,
0.011719164438545704,
-0.010208148509263992,
0.11333944648504257,
-0.02811243198812008,
0.02479841746389866,
0.025811344385147095,
0.0213155597448349,
-0.048918984830379486,
-0.038687702268362045,
-0.1... | 0.127949 |
Thus, creation becomes: .. code-block:: shell-session # tc filter add dev em1 ingress pref 1 handle 1 bpf da obj prog.o sec foobar # tc filter show dev em1 ingress filter protocol all pref 1 bpf filter protocol all pref 1 bpf handle 0x1 prog.o:[foobar] direct-action id 1 tag c5f7825e5dac396f And for the atomic replacem... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.068805031478405,
0.06740190833806992,
0.008591949939727783,
-0.052909135818481445,
-0.0012766080908477306,
-0.042827241122722626,
0.07573145627975464,
-0.0074279592372477055,
0.018638476729393005,
0.061207596212625504,
0.0007091588922776282,
-0.0747029110789299,
-0.009206794202327728,
-... | 0.099867 |
load XDP BPF respectively tc BPF programs with iproute2. There are other various advanced options for the BPF loader that apply both to XDP and tc, some of them are listed here. In the examples only XDP is presented for simplicity. \*\*1. Verbose log output even on success.\*\* The option ``verb`` can be appended for l... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
-0.04371616244316101,
-0.00124258897267282,
0.030532492324709892,
-0.047463592141866684,
0.0625782161951065,
-0.047469884157180786,
0.03342027962207794,
0.09252656251192093,
-0.029874185100197792,
0.012845107354223728,
0.011074651964008808,
-0.06026792898774147,
-0.033521827310323715,
-0.0... | 0.053056 |
the BPF file system. Next the loader will handle all program sections that contain ELF relocation entries for maps, meaning that BPF instructions loading map file descriptors into registers are rewritten so that the corresponding map file descriptors are encoded into the instructions immediate value, in order for the k... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/toolchain.rst | main | cilium | [
0.0003207289264537394,
-0.009595074690878391,
-0.03433762490749359,
-0.06191089749336243,
0.04546590894460678,
-0.018573060631752014,
-0.014342967420816422,
0.03885597363114357,
0.01875290274620056,
-0.045656777918338776,
0.0387786366045475,
0.036773741245269775,
-0.05863484367728233,
-0.1... | 0.199635 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_bpf\_users: Further Reading =============== Mentioned lists of docs, projects, talks, papers, and further reading materials are likely no... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/resources.rst | main | cilium | [
-0.04321272298693657,
-0.014599651098251343,
-0.09947895258665085,
-0.05760309100151062,
0.0825895294547081,
-0.035438939929008484,
0.005317586939781904,
0.09154537320137024,
0.028003022074699402,
-0.051936548203229904,
0.02736564911901951,
-0.05993538349866867,
-0.0005770159768871963,
-0.... | 0.23401 |
to collect metrics through a variety of agents as well as analyze collected systems' performance metrics in real-time or by using historical data. With pmdabcc, PCP has a BCC based performance metrics domain agent which extracts data from the kernel via BPF and BCC. https://github.com/performancecopilot/pcp .. \* \*\*W... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/resources.rst | main | cilium | [
-0.015253630466759205,
-0.01292530819773674,
-0.10180716216564178,
-0.008746065199375153,
0.0017614230746403337,
-0.0028651945758610964,
0.03320314362645149,
0.013063318096101284,
0.0033605482894927263,
-0.021343950182199478,
-0.02872033789753914,
-0.06393095850944519,
-0.04230818897485733,
... | 0.177739 |
The library is used by other kernel projects such as perf and bpftool. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/lib/bpf .. \* \*\*bpftool\*\* bpftool is the main tool for introspecting and debugging BPF programs and BPF maps, and like libbpf is developed by the Linux kernel communit... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/resources.rst | main | cilium | [
-0.04090934991836548,
-0.02999640628695488,
-0.0780518427491188,
-0.04613006114959717,
0.09446628391742706,
-0.03390873968601227,
-0.006942823063582182,
0.08052397519350052,
-0.019844839349389076,
-0.06589953601360321,
0.004082772880792618,
-0.04553687945008278,
-0.05872292071580887,
-0.08... | 0.216929 |
Present, and Future, Ferris Ellis, https://ferrisellis.com/posts/ebpf\_past\_present\_future/ 28. Mar 2017, Analyzing KVM Hypercalls with eBPF Tracing, Suchakra Sharma, https://suchakra.wordpress.com/2017/03/31/analyzing-kvm-hypercalls-with-ebpf-tracing/ 27. Jan 2017, Golang bcc/BPF Function Tracing, Brendan Gregg, htt... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/resources.rst | main | cilium | [
-0.01828615367412567,
0.010745612904429436,
-0.036845654249191284,
-0.036483246833086014,
-0.006337242666631937,
-0.030560173094272614,
-0.00587038416415453,
0.04272386059165001,
-0.05400505289435387,
-0.019891653209924698,
0.033631034195423126,
-0.12033607065677643,
-0.040927160531282425,
... | 0.159212 |
for the Rest of Us, Andy Gospodarek, Jesper Dangaard Brouer, https://netdevconf.info/2.1/slides/apr7/gospodarek-Netdev2.1-XDP-for-the-Rest-of-Us\_Final.pdf 35. Mar 2017, SCALE15x, Pasadena, Linux 4.x Tracing: Performance Analysis with bcc/BPF, Brendan Gregg, https://www.slideshare.net/brendangregg/linux-4x-tracing-perf... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/resources.rst | main | cilium | [
-0.005538312718272209,
0.0009746068972162902,
0.02541913464665413,
-0.06071075052022934,
0.05754933878779411,
-0.09953302890062332,
0.016048332676291466,
0.07143672555685043,
-0.017082151025533676,
-0.00966697558760643,
0.006549172103404999,
-0.004646409302949905,
0.00886205118149519,
-0.0... | 0.1622 |
0. Feb 2014, DevConf.cz, Brno, tc and cls\_bpf: lightweight packet classifying with BPF, Daniel Borkmann, http://borkmann.ch/talks/2014\_devconf.pdf Further Documents ----------------- - Dive into BPF: a list of reading material, Quentin Monnet (https://qmonnet.github.io/whirl-offload/2016/09/01/dive-into-bpf/) - XDP -... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/resources.rst | main | cilium | [
-0.023027919232845306,
-0.052472762763500214,
0.01244270708411932,
-0.08388527482748032,
0.061172567307949066,
-0.014717316254973412,
0.09635636955499649,
0.015645697712898254,
-0.05799616128206253,
-0.007370246108621359,
-0.02250179462134838,
-0.026405390352010727,
-0.03955230861902237,
-... | 0.12167 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_bpf\_architect: BPF Architecture ================ BPF does not define itself by only providing its instruction set, but also by offering ... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.013014661148190498,
-0.016848590224981308,
-0.08939240127801895,
-0.060132794082164764,
0.026179105043411255,
-0.04550046846270561,
-0.026155535131692886,
0.08219607174396515,
0.04533897340297699,
-0.07033544778823853,
0.0015800079563632607,
-0.05635026842355728,
-0.021329637616872787,
... | 0.274556 |
maintained throughout updates via BPF maps. \* BPF provides a stable ABI towards user space, and does not require any third party kernel modules. BPF is a core part of the Linux kernel that is shipped everywhere, and guarantees that existing BPF programs keep running with newer kernel versions. This guarantee is the sa... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.03353578597307205,
-0.07223623245954514,
-0.023471098393201828,
-0.09153547883033752,
0.0706842690706253,
-0.031499359756708145,
0.010646146722137928,
0.04235706478357315,
0.03701185807585716,
-0.04577810689806938,
0.01459694467484951,
0.01910330168902874,
-0.031827013939619064,
-0.0769... | 0.262649 |
Register ``r0`` is also the register containing the exit value for the BPF program. The semantics of the exit value are defined by the type of program. Furthermore, when handing execution back to the kernel, the exit value is passed as a 32 bit value. Registers ``r1`` - ``r5`` are scratch registers, meaning the BPF pro... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.04631365090608597,
-0.08545218408107758,
-0.07688456773757935,
0.006292003206908703,
-0.03472846746444702,
0.01601552590727806,
0.07148940116167068,
0.08886696398258209,
0.0007799954037182033,
-0.013418258167803288,
-0.05794103816151619,
-0.029925957322120667,
-0.03025142475962639,
-0.0... | 0.160208 |
``BPF\_K`` for immediate-based operations respectively). In the latter case, the destination operand is always a register. Both ``dst\_reg`` and ``src\_reg`` provide additional information about the register operands to be used (e.g. ``r0`` - ``r9``) for the operation. ``off`` is used in some instructions to provide a ... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.05481201037764549,
-0.011641236953437328,
-0.07193003594875336,
-0.01926591247320175,
-0.041456349194049835,
-0.050284985452890396,
0.06333602219820023,
0.09011074900627136,
0.026605691760778427,
-0.014117160812020302,
0.04035931080579758,
0.047307711094617844,
-0.02292376197874546,
-0.... | 0.231973 |
to ``off + 1`` is performed, otherwise the next instruction (``0 + 1``) is performed. This fall-through jump logic differs compared to cBPF and allows for better branch prediction as it fits the CPU branch predictor logic more naturally. Available conditions are jeq (``==``), jne (``!=``), jgt (``>``), jge (``>=``), js... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.059037622064352036,
-0.031883370131254196,
-0.05299845337867737,
-0.003692458849400282,
0.004877019673585892,
0.010353866964578629,
-0.04109715297818184,
0.12313523888587952,
-0.028861526399850845,
-0.03805261850357056,
-0.015062947757542133,
-0.01576671563088894,
0.021248361095786095,
... | 0.081099 |
be JIT compiled in a transparent and efficient way, meaning that the JIT compiler only needs to emit a call instruction since the register mapping is made in such a way that BPF register assignments already match the underlying architecture's calling convention. This allows for easily extending the core kernel with new... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.08926986157894135,
-0.06379768997430801,
-0.011149265803396702,
-0.05802348256111145,
0.04016053304076195,
-0.006330331787467003,
0.056323885917663574,
0.09758888930082321,
-0.0010309885255992413,
-0.07442592829465866,
0.023214874789118767,
-0.0801435112953186,
-0.09077367186546326,
-0.... | 0.187607 |
of disadvantages come along with them: User space applications can make use of most file descriptor related APIs, file descriptor passing for Unix domain sockets work transparently, etc, but at the same time, file descriptors are limited to a processes' lifetime, which makes options like map sharing rather cumbersome t... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.02145261876285076,
-0.01247383188456297,
-0.03947661444544792,
-0.023113803938031197,
0.03808174282312393,
0.008832619525492191,
-0.01372036337852478,
0.11667052656412125,
0.05953764542937279,
0.004270227625966072,
0.0430726483464241,
0.0335700698196888,
-0.000858797924593091,
-0.070348... | 0.19455 |
from BPF helper calls and BPF tail calls, a more recent feature that has been added to the BPF core infrastructure is BPF to BPF calls. Before this feature was introduced into the kernel, a typical BPF C program had to declare any reusable code that, for example, resides in headers as ``always\_inline`` such that when ... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.04055710509419441,
0.0198870450258255,
0.013087032362818718,
0.02009330876171589,
0.062311071902513504,
-0.0186210535466671,
0.024693196639418602,
0.0638444796204567,
0.04377597197890282,
-0.027443096041679382,
0.03966948762536049,
0.0033237645402550697,
-0.03895626217126846,
-0.0628458... | 0.088098 |
stack when a program execution is at func2. Once the final function (func3) function terminates, all the previous stack frames will be unwinded and control will get back to the caller of BPF program caller. The kernel introduced additional logic for detecting this feature combination. There is a limit on the stack size... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.037007685750722885,
-0.10847653448581696,
-0.039606716483831406,
-0.05917217209935188,
0.009302915073931217,
-0.04797228425741196,
0.009605031460523605,
0.07809971272945404,
0.07038514316082001,
-0.03543949872255325,
-0.03177119418978691,
-0.04502853751182556,
-0.06498011946678162,
-0.0... | 0.09606 |
future. In case of the ``x86\_64`` JIT compiler, the JITing of the indirect jump from the use of tail calls is realized through a retpoline in case ``CONFIG\_RETPOLINE`` has been set which is the default at the time of writing in most modern Linux distributions. In case of ``/proc/sys/net/core/bpf\_jit\_harden`` set to... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.06532351672649384,
-0.01615949720144272,
-0.008736462332308292,
-0.01232447661459446,
-0.012751175090670586,
-0.05687964707612991,
0.05654403567314148,
0.11431384086608887,
-0.010207093320786953,
-0.06038029491901398,
0.036048904061317444,
0.030378971248865128,
-0.01644873060286045,
-0.... | 0.110069 |
it is also generally recommended for widely used JITs in case of mainstream architectures such as ``x86\_64`` and ``arm64``. Last but not least, the kernel offers an option to disable the use of the ``bpf(2)`` system call for unprivileged users through the ``/proc/sys/kernel/unprivileged\_bpf\_disabled`` sysctl knob. T... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.032231882214546204,
-0.023454908281564713,
-0.11344772577285767,
-0.026093032211065292,
-0.037224385887384415,
-0.04477439075708389,
0.07593165338039398,
0.05322949215769768,
0.008437097072601318,
-0.02806340903043747,
0.07492633908987045,
0.014205661602318287,
-0.010294944047927856,
0.... | 0.158205 |
disabling the unprivileged used for now. This value was added in Linux 5.13. If ``BPF\_UNPRIV\_DEFAULT\_OFF`` is enabled in the kernel config, then this knob will default to 2 instead of 0. This knob does not affect any cBPF programs such as seccomp or traditional socket filters that do not use the ``bpf(2)`` system ca... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/architecture.rst | main | cilium | [
-0.00597672862932086,
-0.01661256141960621,
-0.1099305972456932,
0.0067282929085195065,
-0.020366838201880455,
0.05167944356799126,
-0.010891522280871868,
0.013400783762335777,
0.019708100706338882,
-0.06403397023677826,
0.05755027011036873,
-0.10854437947273254,
-0.013836544007062912,
-0.... | 0.071657 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_bpf\_debug: Debugging and Testing ===================== bpftool ------- bpftool is the main introspection and debugging tool around BPF a... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/debug_and_test.rst | main | cilium | [
0.029444724321365356,
0.019480254501104355,
-0.10370045900344849,
-0.03325369209051132,
0.07907925546169281,
-0.0490276999771595,
0.02182433009147644,
0.05746465176343918,
0.0009509210358373821,
-0.042604830116033554,
0.05610295757651329,
-0.0733519047498703,
0.007670936174690723,
-0.09732... | 0.205181 |
``uid 0``. And the BPF program uses the BPF maps with IDs ``18``, ``20``, ``8``, ``5``, ``6`` and ``14``. The latter IDs can further be used to get information or dump the map themselves. Additionally, bpftool can issue a dump request of the BPF instructions the program runs: .. code-block:: shell-session # bpftool pro... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/debug_and_test.rst | main | cilium | [
-0.04706745222210884,
0.058962397277355194,
-0.1060074046254158,
-0.046643808484077454,
0.019840434193611145,
0.03006812185049057,
0.05647623911499977,
-0.006208574399352074,
-0.05900879576802254,
-0.04442118480801582,
-0.01437580119818449,
-0.08710089325904846,
-0.00047751489910297096,
-0... | 0.120731 |
:align: center Note that the ``xlated`` instruction dump provides the post-verifier BPF instruction image which means that it dumps the instructions as if they were to be run through the BPF interpreter. In the kernel, the verifier performs various rewrites of the original instructions provided by the BPF loader. One e... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/debug_and_test.rst | main | cilium | [
-0.04725771024823189,
0.06026904657483101,
-0.08311404287815094,
-0.10751951485872269,
0.004714665003120899,
-0.017674334347248077,
-0.031231680884957314,
0.0021932381205260754,
-0.03187011927366257,
0.0009573682327754796,
-0.0053350357338786125,
-0.013161529786884785,
0.0070793647319078445,... | 0.04715 |
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 key: 0a 66 1c ee 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 00 value: 00 00 00 00 00... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/debug_and_test.rst | main | cilium | [
0.03685557097196579,
0.007239659316837788,
-0.05017838254570961,
-0.030639974400401115,
0.0595858134329319,
-0.01928717829287052,
0.026244865730404854,
0.016089685261249542,
-0.05679808929562569,
0.002804143587127328,
0.07595955580472946,
-0.06827172636985779,
-0.0030344787519425154,
-0.07... | 0.113558 |
information is included in the BTF. With this command, BTF dump can be formatted either 'raw' or 'c', the one that is used in C code. .. code-block:: shell-session # bpftool btf dump id 60 format c [...] struct ctl\_value { union { \_\_u64 value; \_\_u32 ifindex; \_\_u8 mac[6]; }; }; typedef unsigned int u32; [...] .. ... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/debug_and_test.rst | main | cilium | [
-0.034814655780792236,
0.007039953488856554,
-0.11583677679300308,
0.021311018615961075,
0.06279433518648148,
-0.009052562527358532,
0.03745095431804657,
0.05651617422699928,
-0.051584530621767044,
-0.02736777812242508,
0.002071080496534705,
-0.11492440104484558,
-0.037017110735177994,
-0.... | 0.168606 |
+ : 0: push %rbp 55 1: mov %rsp,%rbp 48 89 e5 4: sub $0x60,%rsp 48 83 ec 60 8: mov %rbx,-0x8(%rbp) 48 89 5d f8 c: mov 0x68(%rdi),%r9d 44 8b 4f 68 10: sub 0x6c(%rdi),%r9d 44 2b 4f 6c 14: mov 0xd8(%rdi),%r8 4c 8b 87 d8 00 00 00 1b: mov $0xc,%esi be 0c 00 00 00 20: callq 0xffffffffe0ff9442 e8 1d 94 ff e0 25: cmp $0x800,%e... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/debug_and_test.rst | main | cilium | [
-0.08899104595184326,
-0.015584392473101616,
-0.05932136997580528,
-0.01863810047507286,
-0.06498956680297852,
-0.07105821371078491,
-0.021599406376481056,
0.049994371831417084,
-0.06518037617206573,
-0.015692275017499924,
0.030702335759997368,
-0.03749559447169304,
0.04313844069838524,
0.... | 0.06495 |
course): .. code-block:: shell-session # perf record -a -e bpf:\* sleep 10 # perf script sock\_example 6197 [005] 283.980322: bpf:bpf\_map\_create: map type=ARRAY ufd=4 key=4 val=8 max=256 flags=0 sock\_example 6197 [005] 283.980721: bpf:bpf\_prog\_load: prog=a5ea8fa30ea6849c type=SOCKET\_FILTER ufd=5 sock\_example 619... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/debug_and_test.rst | main | cilium | [
-0.037385448813438416,
0.04045102000236511,
-0.12189716100692749,
-0.05157243460416794,
0.0005205614143051207,
0.012218008749186993,
0.07037831097841263,
-0.06398776918649673,
-0.018829185515642166,
0.03498365357518196,
-0.031886614859104156,
-0.035145025700330734,
-0.047933969646692276,
-... | 0.052933 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_bpf\_program: Program Types ============= At the time of this writing, there are eighteen different BPF program types available, two of t... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/progtypes.rst | main | cilium | [
0.0024575155694037676,
-0.027086788788437843,
-0.060537438839673996,
-0.04767439141869545,
0.05116810277104378,
-0.07256525009870529,
-0.002752887085080147,
0.08243878930807114,
-0.002241260139271617,
-0.06923471391201019,
0.05271044000983238,
0.008116459473967552,
-0.023507781326770782,
-... | 0.189533 |
kernel equivalent to 4.8 or higher and supports most major 10G or higher networking drivers. As a framework for running BPF in the driver, XDP additionally ensures that packets are laid out linearly and fit into a single DMA'ed page which is readable and writable by the BPF program. XDP also ensures that additional hea... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/progtypes.rst | main | cilium | [
0.03844047710299492,
0.00506323017179966,
0.007201076950877905,
-0.10811199992895126,
0.027976039797067642,
-0.013627857901155949,
0.042439237236976624,
0.08148467540740967,
-0.0480119064450264,
-0.021517373621463776,
0.020314566791057587,
-0.029965665191411972,
-0.05490962043404579,
-0.06... | 0.148139 |
for BPF programs implementing DDoS mitigation mechanisms or firewalling in general. The ``XDP\_PASS`` return code means that the packet is allowed to be passed up to the kernel's networking stack. Meaning, the current CPU that was processing this packet now allocates a ``skb``, populates it, and passes it onwards into ... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/progtypes.rst | main | cilium | [
0.0034271993208676577,
-0.041122157126665115,
0.010963075794279575,
-0.07867732644081116,
0.016909563913941383,
-0.039662547409534454,
0.10593359172344208,
0.023734334856271744,
-0.028111103922128677,
-0.036338284611701965,
0.04357817396521568,
0.002099614590406418,
-0.029607683420181274,
... | 0.137836 |
load-balance packets for passing up the local stack, but on remote, non-XDP processing CPUs. .. \* \*\*Pre-stack filtering / processing\*\* Besides policy enforcement, XDP can also be used for hardening the kernel's networking stack with the help of ``XDP\_DROP`` case, meaning, it can drop irrelevant packets for a loca... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/progtypes.rst | main | cilium | [
-0.03540157154202461,
-0.0028368313796818256,
0.11236226558685303,
-0.07685527205467224,
0.07064060866832733,
-0.04078235477209091,
0.05469536781311035,
0.04335763677954674,
0.0316159725189209,
-0.004333276767283678,
0.054576508700847626,
0.0683179646730423,
-0.031113293021917343,
-0.06782... | 0.128609 |
conference: \* Slides: https://netdevconf.info/2.1/slides/apr6/zhou-netdev-xdp-2017.pdf \* Video: https://youtu.be/YEU2ClcGqts Another example is the integration of XDP into Cloudflare's DDoS mitigation pipeline, which originally was using cBPF instead of eBPF for attack signature matching through iptables' ``xt\_bpf``... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/progtypes.rst | main | cilium | [
-0.0335577018558979,
0.014974859543144703,
0.07745636999607086,
-0.07081156224012375,
0.04802364483475685,
-0.04305563494563103,
0.022839030250906944,
0.05851760506629944,
-0.07071401178836823,
0.02826242707669735,
0.028143486008048058,
-0.008070401847362518,
-0.0010605448624119163,
-0.096... | 0.134497 |
igc | >= 5.13 | | +-------------------------+-------------+ | | i40e | >= 4.13 | | +-------------------------+-------------+ | | ixgbe | >= 4.12 | | +-------------------------+-------------+ | | ixgbevf | >= 4.17 | +------------------------+-------------------------+-------------+ | Marvell | mvneta | >= 5.5 | | +-----... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/progtypes.rst | main | cilium | [
-0.04680686816573143,
0.04869081825017929,
-0.07561240345239639,
-0.019762324169278145,
0.0011715525761246681,
-0.03845555707812309,
-0.008321077562868595,
0.13646341860294342,
-0.02806493081152439,
0.004836331587284803,
0.08610060811042786,
-0.1122654378414154,
0.029546890407800674,
-0.02... | 0.142253 |
case has the advantage that it is rather straight forward to mangle its associated metadata, however, it also contains a lot of protocol specific information (e.g. GSO related state) which makes it difficult to simply switch protocols by solely rewriting the packet data. This is due to the stack processing the packet b... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/progtypes.rst | main | cilium | [
-0.037715308368206024,
0.00698729557916522,
-0.011035269126296043,
-0.12787820398807526,
-0.02491278201341629,
-0.08616558462381363,
0.06023327261209488,
0.06040916219353676,
-0.04053148999810219,
-0.011348002590239048,
0.004929481074213982,
-0.031007608398795128,
0.01817930117249489,
-0.0... | 0.105424 |
``cls\_bpf`` can hold one or more tc BPF programs. In the case where Cilium deploys ``cls\_bpf`` programs, it attaches only a single program for a given hook in ``direct-action`` mode. Typically, in the traditional tc scheme, there is a split between classifier and action modules, where the classifier has one or more a... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/progtypes.rst | main | cilium | [
-0.07158628106117249,
-0.02674580179154873,
-0.08588013797998428,
-0.05418093502521515,
-0.04678767919540405,
-0.07966242730617523,
0.05242931470274925,
0.04364629089832306,
0.05149552598595619,
-0.011451629921793938,
-0.011584984138607979,
-0.0675341859459877,
0.04992091283202171,
-0.0072... | 0.191343 |
has the drawback that several programs would need to parse the packet over and over again resulting in degraded performance. \*\*BPF program return codes\*\* Both the tc ingress and egress hook share the same action return verdicts that tc BPF programs can use. They are defined in the ``linux/pkt\_cls.h`` system header... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/progtypes.rst | main | cilium | [
-0.08733256906270981,
0.007737988606095314,
-0.0017979075200855732,
-0.01604447327554226,
0.024857433512806892,
0.03351717069745064,
0.12520547211170197,
0.038349878042936325,
0.057653699070215225,
0.06969938427209854,
-0.01815253496170044,
-0.01596568152308464,
0.0019610722083598375,
-0.0... | 0.170737 |
\*\*tc BPF FAQ\*\* This section contains a few miscellaneous question and answer pairs related to tc BPF programs that are asked from time to time. \* \*\*Question:\*\* What about ``act\_bpf`` as a tc action module, is it still relevant? \* \*\*Answer:\*\* Not really. Although ``cls\_bpf`` and ``act\_bpf`` share the sa... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/progtypes.rst | main | cilium | [
-0.1167684867978096,
-0.024468498304486275,
-0.033723361790180206,
-0.04868190363049507,
-0.018461965024471283,
0.03573025390505791,
0.15925955772399902,
0.05058886483311653,
0.034119825810194016,
0.015271413139998913,
-0.032929420471191406,
-0.04328155890107155,
0.05197273567318916,
0.056... | 0.133866 |
with veth networking devices connecting the host's initial namespace with the dedicated container's namespace. Since one end of the veth pair has been moved into the container's namespace whereas the other end remains in the initial namespace of the host, all network traffic from the container has to pass through the h... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/progtypes.rst | main | cilium | [
0.028767017647624016,
0.017569195479154587,
0.06182049587368965,
-0.10428430140018463,
-0.01310683786869049,
-0.024420684203505516,
0.059618812054395676,
0.018554706126451492,
-0.01863446645438671,
-0.04397966340184212,
0.010606503114104271,
-0.02974577434360981,
0.01787468232214451,
-0.03... | 0.053276 |
custom annotations for packets pushed into the ring buffer. The latter is also heavily used in Cilium where packet drops can be further annotated to correlate container labels and reasons for why a given packet had to be dropped (such as due to policy violation) in order to provide a richer context. .. \* \*\*Packet sc... | https://github.com/cilium/cilium/blob/main/Documentation/reference-guides/bpf/progtypes.rst | main | cilium | [
-0.079715296626091,
0.032988741993904114,
-0.07467378675937653,
-0.051240224391222,
0.021841105073690414,
0.024758296087384224,
0.08300743997097015,
0.015314573422074318,
0.09588095545768738,
-0.0004722045559901744,
0.013752906583249569,
-0.04409728944301605,
0.0028630192391574383,
-0.0209... | 0.217609 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_dev\_guide: Development ----------- We're happy you're interested in contributing to the Cilium project. This section of the Cilium docum... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/index.rst | main | cilium | [
-0.013348298147320747,
-0.032168302685022354,
-0.05944365635514259,
-0.004789338447153568,
0.06451978534460068,
-0.059762660413980484,
-0.0898667573928833,
0.03013921156525612,
-0.061729952692985535,
0.014631431549787521,
0.04498213157057762,
-0.08610221743583679,
-0.010134726762771606,
-0... | 0.098111 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_bpf\_lvh\_tests: #################################### Run eBPF Tests with Little VM Helper #################################### Prerequis... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/bpf_tests.rst | main | cilium | [
0.005043121986091137,
0.04413419961929321,
-0.06387055665254593,
-0.042833637446165085,
0.04717749357223511,
0.02127452939748764,
-0.09631921350955963,
0.045199520885944366,
-0.019694704562425613,
-0.001877912087365985,
0.07899615913629532,
-0.15913964807987213,
-0.034101713448762894,
-0.0... | 0.091123 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_howto\_contribute: How To Contribute ================= This document shows how to contribute as a community contributor. :ref:`Guidance f... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/contributing_guide.rst | main | cilium | [
-0.07580626755952835,
0.001793297124095261,
-0.04184701293706894,
0.026448136195540428,
0.06474370509386063,
-0.002014181576669216,
-0.08002741634845734,
0.08413781970739365,
-0.044303059577941895,
0.03519479185342789,
0.010277758352458477,
-0.06307331472635269,
0.015888698399066925,
-0.04... | 0.118654 |
repository as ``upstream`` remote: .. code-block:: shell-session git clone https://github.com/${YOUR\_GITHUB\_USERNAME\_OR\_ORG}/cilium.git cd cilium git remote add upstream https://github.com/cilium/cilium.git #. Set up your :ref:`dev\_env`. #. Check the GitHub issues for `good tasks to get started `\_. #. Follow the ... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/contributing_guide.rst | main | cilium | [
-0.030700160190463066,
-0.05852598696947098,
-0.025919992476701736,
-0.03610995411872864,
-0.016680151224136353,
-0.030711593106389046,
-0.07768241316080093,
0.08911743015050888,
0.005865979008376598,
0.10156570374965668,
0.015625935047864914,
-0.1142088770866394,
0.0027189315296709538,
0.... | 0.056664 |
#. (optional) Pick the appropriate milestone for which this PR is being targeted, e.g. ``1.6``, ``1.7``. This is in particular important in the time frame between the feature freeze and final release date. #. If you have permissions to do so, pick the right release-note label. These labels will be used to generate the ... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/contributing_guide.rst | main | cilium | [
-0.018723422661423683,
0.04259685054421425,
-0.03366420045495033,
-0.018104158341884613,
0.02303306758403778,
0.11455869674682617,
-0.01090316567569971,
0.0577043779194355,
-0.02174784243106842,
0.003999796230345964,
0.06489670276641846,
-0.02680058218538761,
-0.09283138811588287,
-0.04399... | 0.031396 |
is ready for review, click \*\*Ready for review\*\* at the bottom of the page. #. Engage in any discussions raised by reviewers and address any changes requested. Set the PR to draft PR mode while you address changes, then click \*\*Ready for review\*\* to re-request review. .. image:: /images/cilium\_request\_review.p... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/contributing_guide.rst | main | cilium | [
-0.11474528163671494,
-0.010431925766170025,
-0.07520823925733566,
0.0648074522614479,
0.01776469126343727,
-0.014193495735526085,
-0.015836570411920547,
0.005597371142357588,
-0.005274672992527485,
0.08338569849729538,
0.03153053671121597,
-0.0726020485162735,
0.00619253795593977,
-0.0408... | 0.095959 |
the review process smoother as GitHub has limitations that prevents reviewers from only seeing the new changes added since the last time they have reviewed a PR. Once all reviews are addressed those commits should be squashed against the commit that introduced those changes. This can be accomplished by the usage of ``g... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/contributing_guide.rst | main | cilium | [
-0.08978308737277985,
-0.04170391336083412,
-0.01811184734106064,
-0.004799806512892246,
0.014394545927643776,
0.0180593840777874,
-0.04926585778594017,
0.049169160425662994,
0.036148734390735626,
0.08194589614868164,
0.04916089400649071,
-0.010274828411638737,
0.014624260365962982,
-0.069... | -0.037947 |
name is the name you convey to people in the community for them to use to identify you as you. The key concern is that your identification is sufficient enough to contact you if an issue were to arise in the future about your contribution. Your real name should not be an anonymous id or false name that misrepresents wh... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/contributing_guide.rst | main | cilium | [
-0.08768922090530396,
-0.011296161450445652,
-0.0771809071302414,
-0.023940540850162506,
-0.051188550889492035,
-0.017973758280277252,
0.0577240064740181,
0.029823826625943184,
0.007882092148065567,
-0.028574064373970032,
0.028165951371192932,
-0.09439169615507126,
-0.014061273075640202,
-... | 0.180798 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_dpconfig: Configuring the Datapath ======================== Introduction ~~~~~~~~~~~~ In order for the Cilium datapath to function, it ne... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/datapath_config.rst | main | cilium | [
-0.015944914892315865,
-0.013679316267371178,
-0.13728033006191254,
-0.02176891639828682,
-0.029799943789839745,
-0.058079835027456284,
-0.007538809906691313,
0.08898165822029114,
-0.04311303049325943,
-0.04413004592061043,
0.03956902399659157,
-0.06686230003833771,
0.010737059637904167,
-... | 0.159846 |
We've declared our global config variable. We've generated Go code and wired up a value from the agent. Now, we need to put the variable to use! In datapath BPF code, we can refer to it using the ``CONFIG()`` macro. This macro resolves to a special variable name representing our configuration value, which could change ... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/datapath_config.rst | main | cilium | [
0.003185214940458536,
0.03352978825569153,
-0.07640735059976578,
0.041059739887714386,
-0.07084879279136658,
0.03273328021168709,
0.07068520784378052,
0.06717495620250702,
-0.08134511858224869,
-0.04079337790608406,
0.03960464149713516,
-0.05346940830349922,
0.0027896990068256855,
-0.02093... | 0.039878 |
be used once per variable per compilation unit. This makes it so the variable cannot be overridden from tests without a workaround, so use sparingly. See :ref:`testing` for more details. .. \_testing: Testing ~~~~~~~ When writing tests, you may need to override configuration values to test different code paths. This ca... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/datapath_config.rst | main | cilium | [
-0.04189777001738548,
-0.034944530576467514,
-0.07347321510314941,
0.08836231380701065,
-0.06765279918909073,
0.018631940707564354,
0.006970648188143969,
0.03896060213446617,
-0.08243986964225769,
-0.025003260001540184,
0.03569471463561058,
-0.016894115135073662,
0.05577453598380089,
-0.00... | -0.015404 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_bgp\_cplane\_contributing: ================= BGP Control Plane ================= This section is specific to :ref:`bgp\_control\_plane` c... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/bgp_cplane.rst | main | cilium | [
-0.019040577113628387,
-0.017860038205981255,
-0.06570205092430115,
-0.017307443544268608,
0.04183618351817131,
-0.040188249200582504,
-0.04928358271718025,
-0.006163517478853464,
-0.016189290210604668,
-0.014779222197830677,
0.022104907780885696,
-0.07441137731075287,
-0.009809915907680988,... | 0.168097 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_hubble\_contributing: Hubble ====== This section is specific to Hubble contributions. Bumping the vendored Cilium dependency ~~~~~~~~~~~~... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/hubble.rst | main | cilium | [
0.009743351489305496,
0.02631092630326748,
-0.04454848915338516,
-0.02870371751487255,
0.03922547027468681,
-0.006119724828749895,
-0.06332514435052872,
0.0535910539329052,
-0.038276370614767075,
-0.04930281266570091,
0.10163449496030807,
-0.0200119037181139,
0.0352485366165638,
-0.0403740... | 0.085807 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_gs\_debugging: ######### Debugging ######### Attaching a Debugger -------------------- Cilium comes with a set of Makefile targets for qu... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/debugging.rst | main | cilium | [
-0.009766676463186741,
0.005707739386707544,
-0.05445165932178497,
-0.0007372907712124288,
0.08443658798933029,
-0.09865786880254745,
-0.047258369624614716,
-0.0016560863004997373,
0.005366972181946039,
0.014224104583263397,
0.05426633730530739,
-0.10069561749696732,
-0.002015443751588464,
... | 0.154903 |
as the libc lookup returns no data. To work around this, denied responses can be configured to be NXDOMAIN by setting ``--tofqdns-dns-reject-response-code=nameError`` on the command line. Monitor Events ~~~~~~~~~~~~~~ The DNS Proxy emits multiple L7 DNS monitor events. One for the request and one for the response (if a... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/debugging.rst | main | cilium | [
-0.003056237706914544,
0.0025524271186441183,
-0.014000206254422665,
-0.048409122973680496,
-0.0795481950044632,
-0.07059624046087265,
-0.032051652669906616,
-0.047097545117139816,
0.07773306965827942,
0.02273217961192131,
-0.04170919954776764,
-0.09127315133810043,
-0.033956486731767654,
... | 0.09689 |
policy, or the matchPattern rule not allowing this domain. It may also be due to a bug in policy propagation to the DNS Proxy. - If the DNS request is allowed, with an explicit message, and it should not be, this may be because a more general policy is in place that allows the request. ``matchPattern: "\*"`` visibility... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/debugging.rst | main | cilium | [
-0.11240390688180923,
-0.010634848847985268,
0.059223294258117676,
-0.07854144275188446,
-0.0834273248910904,
-0.06748752295970917,
-0.012861186638474464,
-0.07883688807487488,
0.009364763274788857,
0.02611958608031273,
-0.031037887558341026,
0.027234787121415138,
-0.02492390014231205,
0.0... | -0.083148 |
This should always succeed, as world catches all IPs not set by more specific entries. This can mean a broken ipcache BPF table. - ``Rejecting DNS query from endpoint due to error``: While checking if the DNS request was allowed (based on Endpoint ID, destination IP:Port and the DNS query) an error occurred. These erro... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/debugging.rst | main | cilium | [
-0.07682495564222336,
0.02770724706351757,
0.034444909542798996,
-0.011688982136547565,
-0.10199645161628723,
-0.07568781077861786,
-0.021152708679437637,
-0.05087484419345856,
0.029308954253792763,
0.01712006889283657,
-0.04911966994404793,
0.017650414258241653,
-0.00004545882984530181,
-... | 0.032271 |
``FQDNSelector`` instance. These receive updates from a global ``NameManager`` in the daemon. They can be listed along with other selectors (roughly corresponding to any L3 rule): .. code-block:: shell-session $ kubectl exec pod/cilium-sbp8v -n kube-system -- cilium-dbg policy selectors SELECTOR USERS IDENTITIES MatchN... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/debugging.rst | main | cilium | [
-0.055769722908735275,
0.06770157814025879,
-0.00020268875232432038,
-0.04702351987361908,
-0.0041753631085157394,
0.002896349411457777,
0.11357434839010239,
-0.04608846455812454,
0.09527350962162018,
0.01694045029580593,
0.03552701696753502,
-0.15255334973335266,
0.01694721169769764,
-0.1... | 0.203034 |
2 Egress fqdn:\* ANY NONE 477 6 reserved:world Note that the labels for identities are resolved here. This can be skipped, or there may be cases where this doesn't occur: .. code-block:: shell-session $ kubectl exec pod/cilium-sbp8v -n kube-system -- cilium-dbg bpf policy get -n 3459 DIRECTION IDENTITY PORT/PROTO PROXY... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/debugging.rst | main | cilium | [
-0.037368569523096085,
0.023989200592041016,
-0.023335790261626244,
-0.05729902908205986,
-0.04716575890779495,
0.00229069497436285,
0.08297620713710785,
-0.031474631279706955,
0.09528698772192001,
0.035016488283872604,
-0.01278812438249588,
-0.10844959318637848,
-0.041056931018829346,
-0.... | 0.129098 |
to collect CPU and memory profiles using ``pprof``. Inspecting profiles can help identify CPU bottlenecks and memory leaks. To capture a profile, take a :ref:`sysdump ` of the cluster with the Cilium CLI or more directly, use the ``cilium-bugtool`` command that is included in the Cilium image after enabling ``pprof`` i... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/debugging.rst | main | cilium | [
0.02485637553036213,
0.013959737494587898,
-0.07363550364971161,
0.015392464585602283,
0.05554020032286644,
-0.08764093369245529,
0.015438921749591827,
0.07883337885141373,
-0.006010872311890125,
0.0002717181632760912,
0.033581338822841644,
-0.14938731491565704,
-0.008472972549498081,
-0.0... | 0.144003 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_dev\_env: Development Setup ================= This page provides an overview of different methods for efficient development on Cilium. De... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/dev_setup.rst | main | cilium | [
0.012744271196424961,
-0.024325231090188026,
-0.02240176498889923,
-0.03311970829963684,
0.005456049460917711,
-0.044568467885255814,
-0.07371402531862259,
0.008321131579577923,
0.06304441392421722,
-0.017188595607876778,
0.05247185006737709,
-0.12885798513889313,
-0.014653767459094524,
-0... | 0.153913 |
the Cilium Agent image and loads it into the cluster. \* ``make kind-image-operator``: Builds only the Cilium Operator (generic) image and loads it into the cluster. \* ``make kind-debug``: Builds all Cilium images with optimizations disabled and ``dlv`` embedded for live debugging enabled and loads the images into the... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/dev_setup.rst | main | cilium | [
-0.02200024388730526,
0.029747916385531425,
-0.021131327375769615,
-0.002862377790734172,
0.02997726947069168,
-0.12292648106813431,
-0.05243377760052681,
0.0036606742069125175,
-0.05237186700105667,
-0.019075728952884674,
0.05100969225168228,
-0.0671192929148674,
0.04388083517551422,
-0.0... | 0.166293 |
white space violations #. Run ``make`` to build your changes. This will also run ``make lint`` and error out on any golang linting errors. The rules are configured in ``.golangci.yaml`` #. Run ``make -C bpf checkpatch`` to validate against your changes coding style and commit messages. #. See :ref:`integration\_testing... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/dev_setup.rst | main | cilium | [
-0.0020547187887132168,
0.01527937687933445,
0.007022415287792683,
-0.009601245634257793,
0.037480831146240234,
-0.0517672523856163,
-0.06392260640859604,
0.08763672411441803,
-0.039343979209661484,
0.018011892214417458,
0.023137478157877922,
-0.0899004191160202,
0.01167146023362875,
0.007... | 0.001536 |
will be faster. Updating k8s is a special case which requires updating k8s libraries in a single change: .. code-block:: shell-session $ # get the tag we are updating (for example ``v0.17.3`` corresponds to k8s ``v1.17.3``) $ # open go.mod and search and replace all ``v0.17.3`` with the version $ # that we are trying t... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/dev_setup.rst | main | cilium | [
-0.03768652677536011,
0.0826149582862854,
0.07473303377628326,
-0.04700234904885292,
0.0016691210912540555,
-0.0617092028260231,
-0.04363931715488434,
0.0332743301987648,
0.012637566775083542,
0.04469064250588417,
0.054068125784397125,
-0.022471342235803604,
-0.025961652398109436,
-0.05394... | 0.038359 |
added in upstream that are not used in Cilium, can be removed. #. Make sure the workflows used on all PRs are running with the new Kubernetes version by default. Make sure the files ``contributing/testing/{ci,e2e}.rst`` are up to date with these changes. #. Update documentation files: - ``Documentation/contributing/tes... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/dev_setup.rst | main | cilium | [
0.014809814281761646,
0.010329115204513073,
-0.001645728130824864,
0.00844571739435196,
-0.010580123402178288,
-0.03611325845122337,
-0.06828619539737701,
0.03232238069176674,
0.09268844872713089,
0.04454444721341133,
-0.011675986461341381,
-0.03764444217085838,
-0.052621498703956604,
0.06... | 0.127469 |
net.ipv6.conf.all.forwarding=1 2) Restart the docker daemon to pick up the new configuration. 3) The new command for creating a network managed by Cilium: .. code-block:: shell-session $ docker network create --ipv6 --driver cilium --ipam-driver cilium cilium-net Now new containers will have an IPv6 address assigned to... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/dev_setup.rst | main | cilium | [
0.07212479412555695,
0.030720267444849014,
-0.028312217444181442,
-0.0018284707330167294,
0.0007337906281463802,
-0.018227877095341682,
-0.07518938928842545,
-0.010426024906337261,
-0.02601093053817749,
0.0182780958712101,
-0.004870709031820297,
-0.10852361470460892,
-0.06834964454174042,
... | 0.058589 |
00000020 75 ff fe 73 11 04 ff 02 00 00 00 00 00 00 00 00 |u..s............| 00000030 00 00 00 00 00 02 85 00 15 b4 00 00 00 00 01 01 |................| 00000040 ae 45 75 73 11 04 00 00 00 00 00 00 |.Eus........| CPU 00: MARK 0x1c56d86c FROM 3978 DEBUG: Handling ICMPv6 type=133 ------------------------------------------... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/dev_setup.rst | main | cilium | [
-0.011690293438732624,
0.04170944541692734,
-0.0012602967908605933,
-0.0003267302818130702,
0.06596501171588898,
-0.07087203860282898,
0.018145238980650902,
0.009929969906806946,
-0.052142105996608734,
0.06213204190135002,
0.04980035498738289,
-0.07115362584590912,
-0.028064144775271416,
-... | 0.079751 |
00 00 00 00 00 |........| | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/dev_setup.rst | main | cilium | [
-0.010963439010083675,
0.09578464180231094,
-0.031721338629722595,
0.009831395000219345,
-0.0616811066865921,
0.035414036363363266,
0.1407068818807602,
0.07025624066591263,
0.02486194670200348,
-0.02272741124033928,
0.006360138300806284,
-0.04063815996050835,
0.06813803315162659,
0.0605637... | 0.055033 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_code\_overview: Code Overview ============= This section provides an overview of the Cilium & Hubble source code directory structure. It ... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/codeoverview.rst | main | cilium | [
-0.011489960364997387,
-0.011798498220741749,
-0.07403779774904251,
0.006743221078068018,
0.053356289863586426,
-0.009106187149882317,
-0.05272161588072777,
0.06670595705509186,
-0.04767489805817604,
-0.01862965151667595,
0.04606984928250313,
-0.059642624109983444,
0.04824352264404297,
-0.... | 0.230414 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_guide-to-the-hive: Guide to the Hive ================= Introduction ~~~~~~~~~~~~ Cilium is using dependency injection (via ``pkg/hive``) ... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/hive.rst | main | cilium | [
-0.055944934487342834,
0.00937928818166256,
-0.009927129372954369,
0.0018896689871326089,
-0.001024614437483251,
-0.07235574722290039,
0.005857471376657486,
0.06126450374722481,
-0.01554059237241745,
0.02606278471648693,
0.06199105829000473,
-0.028767526149749756,
0.013144957832992077,
-0.... | 0.276338 |
isn't a Module, but rather just a plain Invoke. An Invoke // is a cell that, unlike Provide, is always executed. Invoke functions // can depend on values that constructors registered with Provide() can // return. These constructors are then called and their results remembered. var Cell = cell.Invoke(registerHelloHandle... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/hive.rst | main | cilium | [
-0.11067686229944229,
0.014604787342250347,
-0.11029163002967834,
0.026431018486618996,
-0.13167765736579895,
-0.019261179491877556,
-0.012409747578203678,
0.048664093017578125,
-0.05423852428793907,
-0.026512386277318,
0.04362914711236954,
-0.03685178607702255,
0.030791833996772766,
-0.01... | 0.121756 |
now take a look at each of the different kinds of cells, starting with Provide(), which registers one or more constructors with the hive: .. code-block:: go // func Provide(ctors any...) Cell type A interface {} func NewA() A { return A{} } type B interface {} func NewB(A) B { return B{} } // simpleCell provides A and ... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/hive.rst | main | cilium | [
-0.059682317078113556,
-0.025800107046961784,
-0.016188286244869232,
-0.0347093865275383,
-0.053116314113140106,
-0.006873205304145813,
0.040005218237638474,
-0.0037625657860189676,
-0.0633142963051796,
0.029560785740613937,
0.04450732469558716,
-0.05241173878312111,
-0.06593599915504456,
... | 0.09489 |
go // func Decorate(dtor any, cells ...Cell) Cell var Cell = cell.Decorate( myLogger, // The decoration function // These cells will see the objects returned by the 'myLogger' decorator // rather than the objects on the outside. foo.Cell, bar.Cell, ) // myLogger is a decorator that can depend on one or more objects in ... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/hive.rst | main | cilium | [
-0.031122447922825813,
0.06910840421915054,
-0.06084686517715454,
-0.007721907924860716,
-0.09768553823232651,
-0.03430452570319176,
0.04153714329004288,
0.016698190942406654,
-0.040426887571811676,
-0.00720607815310359,
0.00107197358738631,
-0.07187437266111374,
-0.015316708013415337,
0.0... | 0.046858 |
with only public fields. The types of these fields should implement both `metric.WithMetadata `\_ and `prometheus.Collector `\_. The easiest way to get such metrics is to use the types defined in `pkg/metrics/metric `\_. The metric collection struct type returned by the given constructor is made available in the hive j... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/hive.rst | main | cilium | [
-0.026203570887446404,
-0.038580406457185745,
-0.07305409759283066,
-0.015839194878935814,
-0.11324804276227951,
0.0029878478962928057,
0.042970966547727585,
0.048977822065353394,
0.01809540018439293,
-0.027493039146065712,
0.03428564965724945,
-0.15383268892765045,
-0.0735589936375618,
0.... | 0.082492 |
hive is created using ``hive.New()``: .. code-block:: go // func New(cells ...cell.Cell) \*Hive var myHive = hive.New(FooCell, BarCell) ``New()`` creates a new hive and registers all providers to it. Invoke functions are not yet executed as our application may have multiple hives and we need to delay object instantiati... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/hive.rst | main | cilium | [
-0.08095531910657883,
-0.018633278086781502,
-0.07858942449092865,
-0.020001232624053955,
-0.09145650267601013,
-0.025790225714445114,
0.01796726882457733,
0.009949538856744766,
-0.061347149312496185,
0.05110754072666168,
0.02984064817428589,
-0.05275489389896393,
-0.01848248392343521,
-0.... | 0.071029 |
correctness of the cells it depends on which helps with refactoring. \* Utility cells should not Invoke(). Since cells may be used in many applications it makes sense to make them lazy to allow bundling useful utilities into one collection. If a utility cell has an invoke, it may be instantiated even if it is never use... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/hive.rst | main | cilium | [
-0.06732127815485,
0.015633825212717056,
-0.01339076366275549,
-0.035163164138793945,
-0.0993015468120575,
-0.047459766268730164,
-0.004026047885417938,
0.048070743680000305,
-0.09027179330587387,
0.052933260798454285,
-0.009529553353786469,
-0.05677618458867073,
-0.014393429271876812,
-0.... | 0.116746 |
1 SayHello() > stdout '1 SayHello()' matched: 1 SayHello() scripttest.go:72: # The file 'foo' should not be the same as 'bar' (0.000s) > ! cmp foo bar diff foo bar --- foo +++ bar @@ -1,2 +1,1 @@ -foo - +bar --- PASS: TestScript/example.txtar (0.00s) ok github.com/cilium/cilium/contrib/examples/script 0.003s In the tes... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/hive.rst | main | cilium | [
-0.04647902771830559,
0.03748903051018715,
-0.021930426359176636,
0.023843662813305855,
-0.035559918731451035,
-0.09868516772985458,
-0.014612242579460144,
0.06664120405912399,
0.013430253602564335,
0.06323335319757462,
0.05677427351474762,
-0.04582977667450905,
0.0021145441569387913,
-0.0... | 0.151293 |
a reflection based library for building dependency injection frameworks. In dig, you create a container, add in your constructors and then "invoke" to create objects: .. code-block:: go func NewA() (A, error) { /\* ... \*/ } func NewB() B { /\* ... \*/ } func NewC(A, B) (C, error) { /\* ... \*/ } func setupC(C) error /... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/hive.rst | main | cilium | [
-0.1537540853023529,
-0.02879299409687519,
-0.01617160066962242,
-0.013782697729766369,
-0.15279309451580048,
-0.049280788749456406,
-0.02231733873486519,
0.004442636389285326,
-0.026475705206394196,
0.02917131409049034,
-0.004854688886553049,
-0.05902113392949104,
-0.021701401099562645,
0... | 0.080464 |
Cilium Agent and new code should use StateDB. See `pkg/k8s/tables/tables.go `\_, `pkg/k8s/statedb.go `\_ and `PR 34060 `\_. While not a cell by itself, `pkg/k8s/resource `\_ provides an useful abstraction for providing shared event-driven access to Kubernetes objects. Implemented on top of the client-go informer, ``wor... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/hive.rst | main | cilium | [
-0.03588858246803284,
0.05600697547197342,
-0.09354744851589203,
-0.0350821316242218,
-0.09491456300020218,
-0.01552906259894371,
0.03147042915225029,
0.04886658489704132,
0.13074810802936554,
0.05382822826504707,
0.027646200731396675,
-0.05797955393791199,
0.0007431816775351763,
-0.041730... | 0.249285 |
.. only:: not (epub or latex or html) WARNING: You are looking at unreleased Cilium documentation. Please use the official rendered version released here: https://docs.cilium.io .. \_statedb: StateDB in Cilium ================= .. warning:: StateDB and the reconciler are still under active development and the APIs & me... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/statedb.rst | main | cilium | [
-0.08229765295982361,
-0.015607209876179695,
-0.10311104357242584,
0.010040060617029667,
0.0017326001543551683,
-0.01980159804224968,
0.01371585950255394,
0.05578190088272095,
-0.0268098171800375,
0.05669426918029785,
0.023678993806242943,
-0.032700315117836,
0.05978529527783394,
-0.060745... | 0.262947 |
BPF map should be or what routes should be installed. - \*Reconcilers\*: control-loops that observe the desired state tables and reconcile them against a target such as a BPF map or the Linux routing table. The reconciler is usually an instance of the StateDB reconciler which is defined in terms of a table of objects w... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/statedb.rst | main | cilium | [
-0.009594686329364777,
-0.06019093468785286,
-0.04176392778754234,
-0.006093843374401331,
-0.03174648806452751,
0.01618681475520134,
-0.010524982586503029,
0.01115700788795948,
-0.02908174879848957,
0.027011146768927574,
0.02046506106853485,
-0.0037383297458291054,
0.007135780993849039,
-0... | 0.103094 |
an integration test of a module that depends on it. \* Take into account the fact that objects be immutable by designing them to be cheap to shallow-clone. For example this could mean splitting off fields that are constant from creation into their own struct that's referenced from the object. \* Write benchmarks for yo... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/statedb.rst | main | cilium | [
-0.009158586151897907,
0.03854457288980484,
-0.10539893805980682,
0.053040761500597,
-0.06309132277965546,
-0.09517636895179749,
0.01903160661458969,
0.09652632474899292,
-0.013775929808616638,
0.024249693378806114,
0.022729339078068733,
-0.07203364372253418,
0.018498068675398827,
-0.00137... | 0.176213 |
of commands. \\_\_/¯¯\\_\_/ \\_\_/ cilium> help db db Describe StateDB configuration The 'db' command describes the StateDB configuration, showing ... cilium> db Name Object count Zombie objects Indexes Initializers Go type Last WriteTxn health 65 0 identifier, level [] types.Status health (993.6ms ago, locked for 25.7... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/statedb.rst | main | cilium | [
-0.04403490573167801,
-0.029333198443055153,
-0.062069881707429886,
-0.019534997642040253,
-0.021386705338954926,
-0.06552480161190033,
-0.062318526208400726,
0.029957978054881096,
-0.04352186620235443,
0.01733298785984516,
0.0707382783293724,
-0.04643743857741356,
0.018234649673104286,
-0... | 0.174959 |
err := RegisterReconciler( params, tbl, (\*MyObject).Clone, (\*MyObject).SetStatus, (\*MyObject).GetStatus, ops, nil, /\* optional batch operations \*/ ) return err } var Cell = cell.Module( "example", "Example module", ..., cell.Invoke(registerReconciler), ) Insert objects with the ``Status`` set to pending: .. code-b... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/statedb.rst | main | cilium | [
-0.06791459769010544,
-0.061667852103710175,
-0.08345788717269897,
0.08895384520292282,
-0.10598622262477875,
-0.025901557877659798,
0.024456948041915894,
0.048335690051317215,
-0.0066230702213943005,
0.06346012651920319,
0.015210854820907116,
-0.03018837980926037,
0.017066942527890205,
-0... | 0.1001 |
+cilium\_statedb\_table\_contention\_seconds - +cilium\_statedb\_table\_objects - +cilium\_statedb\_table\_revision - +cilium\_statedb\_table\_delete\_trackers - +cilium\_statedb\_table\_graveyard\_objects - +cilium\_statedb\_table\_graveyard\_low\_watermark - +cilium\_statedb\_table\_graveyard\_cleaning\_duration\_sec... | https://github.com/cilium/cilium/blob/main/Documentation/contributing/development/statedb.rst | main | cilium | [
-0.016264041885733604,
-0.02844546176493168,
-0.05104333162307739,
0.01646219938993454,
-0.05237327516078949,
-0.04802336171269417,
-0.014804561622440815,
-0.022228142246603966,
0.03257136419415474,
0.0036699320189654827,
0.05758870393037796,
-0.10469827800989151,
0.04057690501213074,
0.02... | 0.134535 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.