STRUCT ETHTOOL_CMIS_CDB_CMD_ARGS(9)
π NAME
struct ethtool_cmis_cdb_cmd_args β okay bestie, these are the CDB commands execution arguments β¨
β¨ SYNOPSIS
struct ethtool_cmis_cdb_cmd_args {
struct ethtool_cmis_cdb_request req;
u16 max_duration;
u16 msleep_pre_rpl;
u8 read_write_len_ext;
u8 rpl_exp_len;
u8 flags;
char *err_msg;
};
π Members
So like, here's the whole cast of this struct β every single one of them matters, no skipping π
reqβ the CDB command fields, exactly as described in the CMIS standard. Iconic, standards-compliant, we love to see it πmax_durationβ the maximum duration time for command completion, in msec. It's giving "how long are we willing to wait for this to finish" energy β³msleep_pre_rplβ the waiting time before checking the reply, in msec. Yes bestie, we nap before we peek π΄read_write_len_extβ the allowable additional number of byte octets to the LPL in aREADor aWRITEcommand. Lowkey a mouthful but it's important π«Άrpl_exp_lenβ expected reply length in bytes. Set your expectations, queen πflagsβ validation flags for CDB commands. The vibe check flags, fr fr π©err_msgβ the error message to be sent to user space. When things go wrong, we tell the humans π
π SEE ALSO
- Kernel file
./net/ethtool/cmis.hβ go read it, iykyk π struct ethtool_cmis_cdb(9)struct ethtool_cmis_cdb_request(9)struct ethtool_cmis_cdb_rpl_hdr(9)struct ethtool_cmis_cdb_rpl(9)
That's the whole page, bestie β nothing skipped, nothing merged, all the facts intact and slaying πβ¨
Source: ./net/ethtool Β· October 2026 Β· mwah, go forth and check your CDB args ππ¦πΈ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms