#ifndef _CRYPTO_TWOFISH_H #define _CRYPTO_TWOFISH_H #include #define TF_MIN_KEY_SIZE 16 #define TF_MAX_KEY_SIZE 32 #define TF_BLOCK_SIZE 16 struct crypto_tfm; /* Structure for an expanded Twofish key. s contains the key-dependent * S-boxes composed with the MDS matrix; w contains the eight "whitening" * subkeys, K[0] through K[7]. k holds the remaining, "round" subkeys. Note * that k[i] corresponds to what the Twofish paper calls K[i+8]. */ struct twofish_ctx { u32 s[4][256], w[8], k[32]; }; int __twofish_setkey(struct twofish_ctx *ctx, const u8 *key, unsigned int key_len, u32 *flags); int twofish_setkey(struct crypto_tfm *tfm, const u8 *key, unsigned int key_len); #endif png' alt='cgit logo'/> index : net-next.git
net-next plumbingsTobias Klauser
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-06-29 03:00:51 +0200
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2016-07-02 01:52:09 +0200
commit9c744481c003697de453e8fc039468143ba604aa (patch)
treefee5b5bf27c2e4eded3a34486a7de4651af4ff92
parent7b776af66dc462caa7e839cc5c950a61db1f8551 (diff)
PM / hibernate: Do not free preallocated safe pages during image restore
The core image restoration code preallocates some safe pages (ie. pages that weren't used by the image kernel before hibernation) for future use before allocating the bulk of memory for loading the image data. Those safe pages are then freed so they can be allocated again (with the memory management subsystem's help). That's done to ensure that there will be enough safe pages for temporary data structures needed during image restoration. However, it is not really necessary to free those pages after they have been allocated. They can be added to the (global) list of safe pages right away and then picked up from there when needed without freeing. That reduces the overhead related to using safe pages, especially in the arch-specific code, so modify the code accordingly. Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>