Home
last modified time | relevance | path

Searched refs:perfect (Results 1 – 38 of 38) sorted by relevance

/linux-4.4.14/net/sched/
Dcls_tcindex.c42 struct tcindex_filter_result *perfect; /* perfect hash; NULL if none */ member
62 if (p->perfect) { in tcindex_lookup()
63 struct tcindex_filter_result *f = p->perfect + key; in tcindex_lookup()
114 if (p->perfect && handle >= p->alloc_hash) in tcindex_get()
161 if (p->perfect) { in tcindex_delete()
203 kfree(p->perfect); in __tcindex_destroy()
232 kfree(p->perfect); in __tcindex_partial_destroy()
270 if (p->perfect) { in tcindex_set_parms()
273 cp->perfect = kmemdup(p->perfect, in tcindex_set_parms()
275 if (!cp->perfect) in tcindex_set_parms()
[all …]
/linux-4.4.14/arch/s390/numa/
Dmode_emu.c226 enum toptree_level level, bool perfect) in move_level_to_numa_node() argument
233 if (perfect) { in move_level_to_numa_node()
249 enum toptree_level level, bool perfect) in move_level_to_numa() argument
254 move_level_to_numa_node(node, phys, level, perfect); in move_level_to_numa()
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dstmmac.txt30 - snps,perfect-filter-entries: Number of perfect filter entries supported
63 snps,perfect-filter-entries = <128>;
/linux-4.4.14/Documentation/devicetree/bindings/
DABI.txt20 1) Maintainers, don't let perfect be the enemy of good. Don't hold up a
21 binding because it isn't perfect.
/linux-4.4.14/net/decnet/
DTODO29 o Add perfect socket hashing - an idea suggested by Paul Koning. Currently
/linux-4.4.14/fs/gfs2/
DKconfig15 GFS is perfect consistency -- changes made to the filesystem on one
/linux-4.4.14/Documentation/filesystems/
Dgfs2.txt11 features of GFS is perfect consistency -- changes made to the file system
Dmandatory-locking.txt41 In a perfect world all processes would use and honour a cooperative, or
42 "advisory" locking scheme. However, the world isn't perfect, and there's
/linux-4.4.14/Documentation/isdn/
DCREDITS15 For contribution of man-pages, the imontty-tool and a perfect
/linux-4.4.14/arch/arm/boot/dts/
Dsocfpga_arria10.dtsi413 snps,perfect-filter-entries = <128>;
432 snps,perfect-filter-entries = <128>;
451 snps,perfect-filter-entries = <128>;
Dsocfpga.dtsi535 snps,perfect-filter-entries = <128>;
553 snps,perfect-filter-entries = <128>;
/linux-4.4.14/Documentation/input/
Dappletouch.txt71 is not perfect. If finger movements are not recognized anymore, try reloading
/linux-4.4.14/Documentation/video4linux/
DZoran287 LML33 perfect, Buz tolerable (3 or 4 frames dropped per movie)
291 Buz tolerable, LML3 almost perfect (occasional single frame drops)
293 LML33 perfect, Buz tolerable.
302 Buz perfect-tolerable
304 Buz perfect-tolerable
Dsi470x.txt113 V4L minor device allocation and parameter setting is not perfect. A solution is
/linux-4.4.14/Documentation/zh_CN/
DSubmittingPatches392 Andrew Morton, "The perfect patch" (tpp).
/linux-4.4.14/Documentation/hwmon/
Dsubmitting-patches53 through Lindent. Lindent is not perfect, and you may have to do some minor
/linux-4.4.14/Documentation/ja_JP/
DSubmittingPatches692 Andrew Morton, "The perfect patch" (tpp).
/linux-4.4.14/Documentation/dvb/
Dfaq.txt40 That's all far from perfect, but it seems no one has written
/linux-4.4.14/Documentation/
DSubmittingDrivers118 existing driver author to build a single perfect driver.
Dxillybus.txt120 particular, it makes perfect sense to go:
DHOWTO587 perfect these practices (if at all). It's a continuous process of
Dkmemcheck.txt464 warning, so this makes perfect sense. It also seems reasonable to assume that
DSubmittingPatches794 Andrew Morton, "The perfect patch" (tpp).
/linux-4.4.14/Documentation/development-process/
D5.Posting120 Working to create the perfect patch series can be a frustrating process
127 So now you have a perfect series of patches for posting, but the work is
D7.AdvancedTopics76 a simple obsession for the creation of the perfect project history.
D6.Followthrough4 addition of your own engineering skills, have posted a perfect series of
/linux-4.4.14/Documentation/virtual/kvm/
Dtimekeeping.txt365 to a value matching the rest of the system, but a perfect match is usually not
443 In summary, there is no way to guarantee the TSC remains in perfect
606 guest about the host in anything but a perfect implementation of virtualized
/linux-4.4.14/Documentation/devicetree/
Dusage-model.txt98 specific machine. In a perfect world, the specific platform shouldn't
101 Hardware is not perfect though, and so the kernel must identify the
/linux-4.4.14/Documentation/networking/
Ddecnet.txt206 ethernet card doesn't support perfect hashing in its MAC address filter
/linux-4.4.14/Documentation/locking/
Dlockdep-design.txt175 The validator achieves perfect, mathematical 'closure' (proof of locking
/linux-4.4.14/Documentation/usb/
Dusbmon.txt97 It produces slightly longer lines, but otherwise is a perfect superset
/linux-4.4.14/Documentation/vm/
Dcleancache.txt182 or for real kernel-addressable RAM, it makes perfect sense for
/linux-4.4.14/Documentation/power/
Dswsusp.txt99 In a really perfect world:
/linux-4.4.14/Documentation/RCU/
Dtrace.txt123 offline. In a perfect world, this might never happen, but it
/linux-4.4.14/Documentation/scsi/
DChangeLog.sym53c8xx498 If the driver haven't to also raise the SIGP this would be perfect.
Dsym53c8xx_2.txt400 If the firmware of all your devices is perfect enough, all the
Dncr53c8xx.txt559 If the firmware of all your devices is perfect enough, all the
/linux-4.4.14/Documentation/sound/alsa/
DHD-Audio.txt56 dead. However, this detection isn't perfect on some devices. In such