Nvmed: Restrict telemetry to Data Area 1

Restrict telemetry to Data Area 1 to prevent bmcweb from timing out
when pulling log page 0x7

This is to support E1.S SSD left shift development

Tested: https://paste.googleplex.com/6177104015261696

Google-Bug-Id: 491346412
Change-Id: I2f6d3602cddba2b03791dcdfab5ea339c9b67b6d
Signed-off-by: Agrim Bharat <agrimbharat@google.com>

src/NVMeMi.cpp

diff --git a/src/NVMeMi.cpp b/src/NVMeMi.cpp
index 015d968..b528ba5 100644
--- a/src/NVMeMi.cpp
+++ b/src/NVMeMi.cpp
@@ -878,12 +878,12 @@
         return rc;
     }
 
-    // Restrict the telemetry log to Data Area 1 and 2. Getting Data Area 3
-    // OOB is not suitable due to its possible size. Data Area 3 can be up to
-    // 30000 data blocks with each block being 512 bytes in size. Restricting
-    // to Area 1 and 2.
+    // Restrict the telemetry log to Data Area 1. DA1 and DA2 contain the same
+    // essential telemetry data, as DA2 is a superset of DA1 and no additional
+    // unique information is populated in DA2. Limiting to DA1 is sufficient and
+    // reduces OOB data transfer.
     size = static_cast<uint32_t>(
-               (boost::endian::little_to_native(log.dalb2) + 1)) *
+               (boost::endian::little_to_native(log.dalb1) + 1)) *
            NVME_LOG_TELEM_BLOCK_SIZE;
     return rc;
 }