Hi, > -----Original Message----- > From: Stephen Hemminger <[email protected]> > Sent: Monday, August 10, 2026 8:46 PM > To: Gagandeep Singh <[email protected]> > Cc: [email protected]; [email protected]; Hemant Agrawal > <[email protected]> > Subject: Re: [PATCH 6/6] crypto/dpaa2_sec: add support for env variables > > On Mon, 10 Aug 2026 16:59:51 +0530 > Gagandeep Singh <[email protected]> wrote: > > > Allow driver configuration via environment variables as a fallback > > when devargs are not provided. After processing devargs (or when > > devargs are absent), check DRIVER_STRICT_ORDER and > DRIVER_DUMP_MODE > > environment variables to set en_loose_ordered and dpaa2_sec_dp_dump. > > > > This lets users configure the driver without modifying EAL arguments, > > useful in environments where command-line access is restricted. > > > > Signed-off-by: Gagandeep Singh <[email protected]> > > No. This is bad precedent. DPDK has a method for configuration. > Adding AdHoc environment variables creates chaos.
I understand the concern. The devargs are already presents. The motivation was mainly customer support. In many deployments, users cannot easily modify EAL/devargs but can set environment variables without the need to update and recompile their binaries, making it easier to enable temporary debugging in the field.
