summaryrefslogtreecommitdiff
path: root/tprintf.c
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2015-10-19 17:20:26 +0200
committerTobias Klauser <tklauser@distanz.ch>2015-10-19 17:25:33 +0200
commitf5f002fd8966b78ece5b4e1757e639379619670a (patch)
tree496b04c29c2c184f770407ea25e47ea6abd9f630 /tprintf.c
parent83e0c196b189513318093a6bf94f783c95e37b4f (diff)
netsniff-ng: nlmsg: Display raw data if family is unknown
Currently we only support full dissection of RTNL netlink messages. For non-RTNL message we only print the header and omit the data. Change this behavior and print a full ascii/hex dump of the remaining data (like it is done in dissector_entry_point() for trailing data after all known protocols have been processed) to give the user a chance to still inspect the message content. Reported-by: Geoff Ladwig <gladwig@verdantnetworks.com> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'tprintf.c')
0 files changed, 0 insertions, 0 deletions
down the underlying physical pages of the address space, and save from them need to track the validity of the mappings. Rather, the HCA requests the latest translations from the OS when pages are not present, and the OS invalidates translations which are no longer valid due to either non-present pages or mapping changes. In existing ODP implementation applications is needed to register memory buffers for communication, though registered memory regions need not have valid mappings at registration time. This patch set performs the following steps to expand current ODP implementation: 1. It refactors UMR to support large regions, by introducing generic function to perform HCA translation table modifications. This function supports both atomic and process contexts and is not limited by number of modified entries. This function allows to enable reallocated memory regions of arbitrary size, so adding MR cache buckets to support up to 16GB MRs. 2. It changes page fault event format and refactor page faults logic together with addition of atomic support. 3. It prepares mlx5 core code to support implicit registration with simplified and relaxed semantics. Implicit ODP semantics allows to applications provide special memory key that represents their complete address space. Thus all IO accesses referencing to this key (with proper access rights associated with the key) wouldn't need not register any virtual address range. Thanks, Artemy, Ilya and Leon v1->v2: - Don't use 'inline' in .c files ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include')