diff options
author | Herbert Xu <herbert@gondor.apana.org.au> | 2017-02-11 19:26:47 +0800 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-02-17 12:28:35 -0500 |
commit | da20420f83ea0fbcf3d03afda08d971ea1d8a356 (patch) | |
tree | 0a6a08124301510af4c6f6926efc9ae7afd8c03f /Documentation/Intel-IOMMU.txt | |
parent | 40f9f439706073b4b0a654b3b99e18296b7990b3 (diff) | |
download | op-kernel-dev-da20420f83ea0fbcf3d03afda08d971ea1d8a356.zip op-kernel-dev-da20420f83ea0fbcf3d03afda08d971ea1d8a356.tar.gz |
rhashtable: Add nested tables
This patch adds code that handles GFP_ATOMIC kmalloc failure on
insertion. As we cannot use vmalloc, we solve it by making our
hash table nested. That is, we allocate single pages at each level
and reach our desired table size by nesting them.
When a nested table is created, only a single page is allocated
at the top-level. Lower levels are allocated on demand during
insertion. Therefore for each insertion to succeed, only two
(non-consecutive) pages are needed.
After a nested table is created, a rehash will be scheduled in
order to switch to a vmalloced table as soon as possible. Also,
the rehash code will never rehash into a nested table. If we
detect a nested table during a rehash, the rehash will be aborted
and a new rehash will be scheduled.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/Intel-IOMMU.txt')
0 files changed, 0 insertions, 0 deletions