Bluetooth: Fine-tune debug-based stack size increase
Now that printk is the default backend for logging the overhead is not as bad as with printf. 160 seems to be roughly the worst case amount of overhead that debug logs now cause. Change-Id: Ia5937b7318e00cc31c72fa1702c73a57bca0603a Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
This commit is contained in:
parent
f53388dbb9
commit
047c6eacf7
@ -47,8 +47,8 @@ void bt_log(int prio, const char *fmt, ...);
|
||||
__func__, ##__VA_ARGS__)
|
||||
#define BT_INFO(fmt, ...) bt_log(BT_LOG_INFO, fmt, ##__VA_ARGS__)
|
||||
|
||||
/* Enabling debug increases stack size requirement considerably */
|
||||
#define BT_STACK_DEBUG_EXTRA 512
|
||||
/* Enabling debug increases stack size requirement */
|
||||
#define BT_STACK_DEBUG_EXTRA 160
|
||||
|
||||
#elif defined(CONFIG_BLUETOOTH_DEBUG_LOG)
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user