On Sat, 30 Apr, at 10:33:32AM, Jeremy Compostella wrote: > Ingo Molnar <mingo@xxxxxxxxxx> writes: > > > > Hm, can reboot notifiers do non-atomic allocations? > The reboot notifier chain is a blocking notifier chain. AFAIK, it > allows non-atomic allocation, right ? I would assume so, yes. > > Why is efivar_entry so huge? > efivar_entry structure include two "big" arrays of 1024 bytes each for > the EFI variable name and data. Yeah. This is partially historical in that the EFI variable code has always had these arrays. But it's also that if you're dealing with EFI variables you always want someplace to cache the data and name, so no one has ever proposed to split out the data/name from struct efivar_entry. We've never put them on the stack before either ;) -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|