Searched refs:fanout (Results 1 – 18 of 18) sorted by relevance
/kernel/linux/linux-5.10/net/packet/ |
D | diag.c | 118 if (po->fanout) { in pdiag_put_fanout() 121 val = (u32)po->fanout->id | ((u32)po->fanout->type << 16); in pdiag_put_fanout()
|
D | internal.h | 112 struct packet_fanout *fanout; member
|
D | af_packet.c | 305 if (po->fanout) in __register_prot_hook() 335 if (po->fanout) in __unregister_prot_hook() 1480 struct packet_fanout *f = po->fanout; in __fanout_link() 1493 struct packet_fanout *f = po->fanout; in __fanout_unlink() 1517 return ptype->af_packet_priv == pkt_sk(sk)->fanout; in match_fanout_group() 1566 __fanout_set_data_bpf(po->fanout, new); in fanout_set_data_cbpf() 1587 __fanout_set_data_bpf(po->fanout, new); in fanout_set_data_ebpf() 1594 switch (po->fanout->type) { in fanout_set_data() 1673 if (po->fanout) in fanout_add() 1755 WRITE_ONCE(po->fanout, match); in fanout_add() [all …]
|
/kernel/linux/linux-5.10/kernel/rcu/ |
D | Kconfig | 117 int "Tree-based hierarchical RCU fanout value" 124 This option controls the fanout of hierarchical implementations 137 int "Tree-based hierarchical RCU leaf-level fanout value" 145 This option controls the leaf-level fanout of hierarchical 149 want the default because the smaller leaf-level fanout keeps 158 fanout to a large number will likely cause problematic
|
/kernel/linux/linux-5.10/fs/ubifs/ |
D | commit.c | 570 sz = sizeof(struct idx_node) + ubifs_idx_node_sz(c, c->fanout) - in dbg_check_old_index() 602 if (child_cnt < 1 || child_cnt > c->fanout) { in dbg_check_old_index() 704 ubifs_dump_node(c, idx, ubifs_idx_node_sz(c, c->fanout)); in dbg_check_old_index() 710 ubifs_dump_node(c, &i->idx, ubifs_idx_node_sz(c, c->fanout)); in dbg_check_old_index()
|
D | sb.c | 202 sup->fanout = cpu_to_le32(DEFAULT_FANOUT); in create_default_filesystem() 457 if (c->fanout < UBIFS_MIN_FANOUT || in validate_sb() 458 ubifs_idx_node_sz(c, c->fanout) > c->leb_size) { in validate_sb() 719 c->fanout = le32_to_cpu(sup->fanout); in ubifs_read_superblock()
|
D | tnc_misc.c | 297 if (znode->child_cnt > c->fanout || znode->level > UBIFS_MAX_LEVELS) { in read_znode() 299 c->fanout, znode->child_cnt); in read_znode()
|
D | tnc.c | 2087 ubifs_assert(c, n >= 0 && n <= c->fanout); in tnc_insert() 2092 if (znode->child_cnt < c->fanout) { in tnc_insert() 2093 ubifs_assert(c, n != c->fanout); in tnc_insert() 2127 if (n == c->fanout) { in tnc_insert() 2134 } else if (appending && n != c->fanout) { in tnc_insert() 2138 if (n >= (c->fanout + 1) / 2) { in tnc_insert() 2146 move = c->fanout - keep; in tnc_insert() 2155 keep = c->fanout; in tnc_insert() 2158 keep = (c->fanout + 1) / 2; in tnc_insert() 2159 move = c->fanout - keep; in tnc_insert() [all …]
|
D | budget.c | 642 f = c->fanout > 3 ? c->fanout >> 1 : 2; in ubifs_reported_space()
|
D | ubifs-media.h | 667 __le32 fanout; member
|
D | super.c | 684 c->fanout * sizeof(struct ubifs_zbranch); in init_constants_sb() 690 tmp = ubifs_idx_node_sz(c, c->fanout); in init_constants_sb() 1582 dbg_gen("tree fanout: %d", c->fanout); in mount_ubifs() 1594 UBIFS_MAX_DENT_NODE_SZ, ubifs_idx_node_sz(c, c->fanout)); in mount_ubifs()
|
D | debug.c | 374 pr_err("\tfanout %u\n", le32_to_cpu(sup->fanout)); in ubifs_dump_node() 540 for (i = 0; i < n && i < c->fanout; i++) { in ubifs_dump_node() 886 if (znode->child_cnt <= 0 || znode->child_cnt > c->fanout) { in ubifs_dump_znode() 1291 if (znode->child_cnt <= 0 || znode->child_cnt > c->fanout) { in dbg_check_znode() 1299 if (znode->iip < 0 || znode->iip >= c->fanout) { in dbg_check_znode()
|
D | tnc_commit.c | 442 buf_len = ubifs_idx_node_sz(c, c->fanout); in layout_in_empty_space()
|
D | ubifs.h | 1345 int fanout; member
|
/kernel/linux/linux-5.10/drivers/fsi/ |
D | Kconfig | 44 a high target device fanout.
|
/kernel/linux/linux-5.10/Documentation/RCU/Design/Data-Structures/ |
D | Data-Structures.rst | 55 a two-level tree with 64 leaves can accommodate 1,024 CPUs, with a fanout 56 of 64 at the root and a fanout of 16 at the leaves. 61 | Why isn't the fanout at the leaves also 64? | 67 | leaf ``rcu_node`` structures have fanout of 64, the contention on | 69 | on a wide variety of systems has shown that a fanout of 16 works well | 73 | thousands of CPUs may demonstrate that the fanout for the non-leaf | 79 | non-leaf fanout as needed. | 646 given the fanout specified by ``RCU_FANOUT`` and ``RCU_FANOUT_LEAF``. 660 number of CPUs by the fanout supported by the number of levels from the 665 fanout.
|
/kernel/linux/linux-5.10/Documentation/networking/ |
D | packet_mmap.rst | 599 AF_PACKET fanout mode 602 In the AF_PACKET fanout mode, packet reception can be load balanced among 605 Currently implemented fanout policies are: 726 fprintf(stderr, "Unknown fanout type [%s]\n", argp[2]); 770 So it seems to be a good candidate to be used with packet fanout.
|
/kernel/linux/linux-5.10/Documentation/filesystems/ |
D | ubifs-authentication.rst | 293 | ... | (fanout: 8)
|