Task notification vs queue performance in FreeRTOS

Introduction

Task notifications and queues are ways tasks in FreeRTOS communicate. Understanding their speed helps you pick the best one for your program.

You want to send simple signals or small data between tasks quickly.

You need to send multiple messages or larger data chunks between tasks.

You want to avoid blocking a task for too long while waiting for data.

You want to optimize your system for speed and memory use.

You want to handle task synchronization efficiently.

Syntax

FreeRTOS

/* Task Notification Example */
void vTaskFunction(void *pvParameters) {
    uint32_t ulNotificationValue;
    for (;;) {
        /* Wait for notification */
        xTaskNotifyWait(0x00, 0xffffffff, &ulNotificationValue, portMAX_DELAY);
        /* Process notification value */
    }
}

/* Queue Example */
QueueHandle_t xQueue;

void vSenderTask(void *pvParameters) {
    int dataToSend = 100;
    for (;;) {
        xQueueSend(xQueue, &dataToSend, portMAX_DELAY);
    }
}

void vReceiverTask(void *pvParameters) {
    int receivedData;
    for (;;) {
        xQueueReceive(xQueue, &receivedData, portMAX_DELAY);
        /* Process receivedData */
    }
}

Task notifications are like fast signals with optional 32-bit data.

Queues can hold multiple items and are more flexible but slower.

Examples

This shows how to check if a queue is empty without waiting.

FreeRTOS

/* Empty queue scenario */
QueueHandle_t xQueue = xQueueCreate(5, sizeof(int));
int receivedValue;
if (xQueueReceive(xQueue, &receivedValue, 0) == pdPASS) {
    // Got data
} else {
    // Queue empty
}

Task waits for a single notification signal.

FreeRTOS

/* Single element notification */
uint32_t notificationValue = 0;
xTaskNotifyGive(taskHandle);
if (xTaskNotifyWait(0, 0xffffffff, &notificationValue, portMAX_DELAY) == pdTRUE) {
    // Notification received
}

Task blocks until it gets a notification.

FreeRTOS

/* Notification at task start */
// Task waits indefinitely for notification before proceeding
xTaskNotifyWait(0, 0xffffffff, NULL, portMAX_DELAY);

Shows what happens if you try to send to a full queue without waiting.

FreeRTOS

/* Queue full scenario */
QueueHandle_t xQueue = xQueueCreate(2, sizeof(int));
int data = 10;
xQueueSend(xQueue, &data, 0);
xQueueSend(xQueue, &data, 0);
BaseType_t result = xQueueSend(xQueue, &data, 0);
// result will be errQUEUE_FULL

Sample Program

This program creates two tasks: one waits for a task notification, the other waits for data from a queue. It sends a notification and queue data, then prints what each task receives.

FreeRTOS

#include "FreeRTOS.h"
#include "task.h"
#include "queue.h"
#include <stdio.h>

QueueHandle_t xQueue;
TaskHandle_t xTaskHandle;

void vTaskNotificationReceiver(void *pvParameters) {
    uint32_t ulNotificationValue;
    printf("TaskNotificationReceiver: Waiting for notification...\n");
    xTaskNotifyWait(0x00, 0xffffffff, &ulNotificationValue, portMAX_DELAY);
    printf("TaskNotificationReceiver: Received notification with value %lu\n", ulNotificationValue);
    vTaskDelete(NULL);
}

void vQueueReceiver(void *pvParameters) {
    int receivedValue;
    printf("QueueReceiver: Waiting for queue data...\n");
    xQueueReceive(xQueue, &receivedValue, portMAX_DELAY);
    printf("QueueReceiver: Received queue data %d\n", receivedValue);
    vTaskDelete(NULL);
}

int main(void) {
    xQueue = xQueueCreate(1, sizeof(int));
    if (xQueue == NULL) {
        printf("Failed to create queue\n");
        return 1;
    }

    xTaskCreate(vTaskNotificationReceiver, "NotifyReceiver", configMINIMAL_STACK_SIZE, NULL, 1, &xTaskHandle);
    xTaskCreate(vQueueReceiver, "QueueReceiver", configMINIMAL_STACK_SIZE, NULL, 1, NULL);

    printf("Sending notification to task...\n");
    xTaskNotifyGive(xTaskHandle);

    int dataToSend = 42;
    printf("Sending data to queue...\n");
    xQueueSend(xQueue, &dataToSend, 0);

    vTaskStartScheduler();

    // Should never reach here
    return 0;
}

Important Notes

Task notifications are faster because they avoid the overhead of queues and copying data.

Queues use more memory and CPU time but can hold multiple messages and larger data.

Common mistake: Using task notifications for large or multiple messages instead of queues.

Use task notifications for simple signaling or small data; use queues for complex or multiple messages.

Summary

Task notifications are lightweight and fast for simple signals.

Queues are flexible and can hold multiple or larger messages but are slower.

Choose based on your data size and communication needs.

Practice

1. Which statement best describes the performance difference between FreeRTOS task notifications and queues?

easy

A. Task notifications and queues have the same performance.

B. Queues are faster and use less memory than task notifications.

C. Task notifications are faster and use less memory than queues.

D. Queues are only used for signaling, not data transfer.

Solution

1. Step 1: Understand task notifications

   Task notifications are designed as lightweight signals between tasks, using minimal resources.

2. Step 2: Compare with queues

   Queues provide more flexibility but require more memory and processing time, making them slower.

3. Final Answer:

   Task notifications are faster and use less memory than queues. -> Option C

4. Quick Check:

   Task notifications = faster, less memory [OK]

Hint: Task notifications are lightweight signals, queues hold data [OK]

Common Mistakes:

• Thinking queues are always faster
• Confusing signaling with data transfer
• Assuming task notifications can hold large data

2. Which of the following is the correct syntax to send a task notification in FreeRTOS?

easy

A. xTaskNotifyGive(taskHandle);

B. xQueueSend(queueHandle, &data, portMAX_DELAY);

C. xTaskNotifySend(taskHandle, 0);

D. xQueueReceive(queueHandle, &data, 0);

Solution

1. Step 1: Identify task notification sending functions

   The function xTaskNotifyGive() is used to send a notification to a task.

2. Step 2: Differentiate from queue functions

   xQueueSend() and xQueueReceive() are queue operations, not task notifications.

3. Final Answer:

   xTaskNotifyGive(taskHandle); -> Option A

4. Quick Check:

   Send notification = xTaskNotifyGive() [OK]

Hint: Use xTaskNotifyGive() to send notifications, not queue functions [OK]

Common Mistakes:

• Using queue functions to send notifications
• Confusing xTaskNotifySend with xTaskNotifyGive
• Incorrect parameters in notification functions

3. Consider the following code snippet in FreeRTOS:

uint32_t value = 0;
if (xTaskNotifyWait(0x00, 0xFFFFFFFF, &value, 0) == pdTRUE) {
    // Notification received
    process(value);
} else {
    // No notification
    process(0);
}

What will happen if a task notification with value 5 was sent before this check?

medium

A. process(0) will be called because timeout is zero.

B. process(5) will be called because notification value is received.

C. The code will block until a notification arrives.

D. An error occurs because value is not initialized.

Solution

1. Step 1: Understand xTaskNotifyWait behavior

   This function checks for a notification and retrieves its value if available, returning pdTRUE.

2. Step 2: Analyze the timeout and notification value

   Since a notification with value 5 was sent before, the function returns immediately with pdTRUE and sets value to 5.

3. Final Answer:

   process(5) will be called because notification value is received. -> Option B

4. Quick Check:

   Notification received = process(value) [OK]

Hint: If notification sent, xTaskNotifyWait returns true immediately [OK]

Common Mistakes:

• Assuming zero timeout causes blocking
• Ignoring the notification value received
• Thinking uninitialized value causes error

4. Given this FreeRTOS code snippet, what is the main issue?

uint32_t notifyValue;
if (xTaskNotifyWait(0, 0xFFFFFFFF, ¬ifyValue, portMAX_DELAY) == pdTRUE) {
    // Process notification
    process(notifyValue);
}
// Later
xQueueSend(queueHandle, &data, 0);

medium

A. xQueueSend is called without checking if the queue is full.

B. xTaskNotifyWait cannot be used with queues.

C. notifyValue is not initialized before use.

D. Using portMAX_DELAY in xTaskNotifyWait can cause indefinite blocking.

Solution

1. Step 1: Analyze xTaskNotifyWait usage

   Using portMAX_DELAY causes the task to block indefinitely until a notification arrives.

2. Step 2: Consider implications

   This indefinite block can cause deadlocks if notifications are not sent, which is a common issue.

3. Final Answer:

   Using portMAX_DELAY in xTaskNotifyWait can cause indefinite blocking. -> Option D

4. Quick Check:

   portMAX_DELAY = indefinite block risk [OK]

Hint: portMAX_DELAY blocks forever; use timeout carefully [OK]

Common Mistakes:

• Ignoring blocking behavior of portMAX_DELAY
• Assuming notifyValue must be initialized
• Confusing queue and notification usage

5. You need to send multiple integer values from one task to another in FreeRTOS with minimal delay. Which approach is best for performance and why?

hard

A. Use task notifications only for signaling and queues for data transfer.

B. Use a queue to send each integer separately, ensuring order and data integrity.

C. Use global variables protected by mutexes to share data.

D. Use task notifications with bitwise encoding to send multiple values quickly.

Solution

1. Step 1: Understand task notifications limitations

   Task notifications are fast but designed for simple signals or small data (like a single 32-bit value).

2. Step 2: Consider queues for multiple data items

   Queues can hold multiple messages and maintain order, suitable for sending multiple integers reliably.

3. Step 3: Choose best practice

   Use task notifications for signaling and queues for actual data transfer to balance performance and correctness.

4. Final Answer:

   Use task notifications only for signaling and queues for data transfer. -> Option A

5. Quick Check:

   Notifications = signals, queues = data [OK]

Hint: Notifications signal; queues transfer multiple data items [OK]

Common Mistakes:

• Trying to encode multiple values in notifications
• Ignoring data integrity with global variables
• Assuming notifications can replace queues for data