mpi3mr_conve...hy_link_rate(9)
β¨ mpi3mr_conve...hy_link_rate(9) β¨
okay so bestie, welcome to the mpi3mr_conve...hy_link_rate(9) page from the Kernel API Manual β yes the header truncates it, no we're not gonna be weird about it, the whole thing is mpi3mr_convert_phy_link_rate and it's lowkey adorable. it's a tiny little translator function and honestly it's giving "one job, does it well" main character energy π
πΈ NAME πΈ
mpi3mr_convert_phy_link_rate β literally it's just a name, there's no fancy one-liner in the original, and we respect that. it converts a phy link rate. that's the whole vibe π¦
π SYNOPSIS π
enum sas_linkrate mpi3mr_convert_phy_link_rate (u8 link_rate );
like, look at her. one arg, one return type, no notes. iconic β¨
π ARGUMENTS π
link_rateβ the link rate, expressed in the format the MPI header defines. not the SAS format! the MPI one!! this is the before picture, bestie π«Ά
π§ DESCRIPTION π§
okay so here's the tea: link_rate comes in all dressed up in mpi format, and this function converts it into the form the sas_transport layer wants. it's a glow-up montage. it's a translation. it's the vibe check between two different worlds π
no cap, that's the entire described behaviour β convert link_rate from mpi format into sas_transport layer form. we're not inventing extra steps, that would be rude π
β RETURN β
it hands you back a valid SAS transport layer defined link rate. a real one. a legit one. go forth and use it π
π₯ SEE ALSO π₯
bestie. BUCKLE UP. this list is a whole friend group and we are not leaving anybody out, everybody gets a shoutout at the party π
first, the file this whole situation lives in:
- Kernel file
./drivers/scsi/mpi3mr/mpi3mr_transport.c
and now the full squad, in order, exactly as the page gives them:
mpi3mr_post_transport_req(9)mpi3mr_report_manufacture(9)__mpi3mr_expander_find_by_handle(9)mpi3mr_is_expander_device(9)mpi3mr_get_sas_address(9)__mpi3mr_get_tgtdev_by_addr(9)mpi3mr_get_tgtdev_by_addr(9)mpi3mr_remove_device_by_sas_address(9)__mpi3mr_get_tgtdev_by_addr_and_rphy(9)mpi3mr_expander_find_by_sas_address(9)__mpi3mr_sas_node_find_by_sas_address(9)mpi3mr_parent_present(9)mpi3mr_delete_sas_phy(9)mpi3mr_add_sas_phy(9)mpi3mr_add_phy_to_an_existing_port(9)mpi3mr_delete_sas_port(9)mpi3mr_del_phy_from_an_existing_port(9)mpi3mr_sas_port_sanity_check(9)mpi3mr_set_identify(9)mpi3mr_add_host_phy(9)mpi3mr_add_expander_phy(9)mpi3mr_alloc_hba_port(9)mpi3mr_get_hba_port_by_id(9)mpi3mr_update_links(9)mpi3mr_sas_host_refresh(9)mpi3mr_sas_host_add(9)mpi3mr_sas_port_add(9)mpi3mr_sas_port_remove(9)struct host_port(9)mpi3mr_update_mr_sas_port(9)mpi3mr_refresh_sas_ports(9)mpi3mr_refresh_expanders(9)mpi3mr_expander_node_add(9)mpi3mr_expander_add(9)mpi3mr_expander_node_remove(9)mpi3mr_expander_remove(9)mpi3mr_get_sas_negotiated_logical_linkrate(9)mpi3mr_report_tgtdev_to_sas_transport(9)mpi3mr_remove_tgtdev_from_sas_transport(9)mpi3mr_get_port_id_by_sas_phy(9)mpi3mr_get_port_id_by_rphy(9)mpi3mr_get_expander_phy_error_log(9)mpi3mr_transport_get_linkerrors(9)mpi3mr_transport_get_enclosure_identifier(9)mpi3mr_transport_get_bay_identifier(9)mpi3mr_expander_phy_control(9)mpi3mr_transport_phy_reset(9)mpi3mr_transport_phy_enable(9)mpi3mr_transport_phy_speed(9)mpi3mr_map_smp_buffer(9)mpi3mr_unmap_smp_buffer(9)mpi3mr_transport_smp_handler(9)
see? everybody invited. nobody left on read π«Ά
ngl this one's short and sweet β no warnings, no bugs section, no deprecation drama. just a convert and a return. take the win, bestie π
and that's the page!! delivered to you from ./drivers/scsi/mpi3mr, dated October 2026, under the header mpi3mr_conve...hy_link_rate(9) β mwah, go convert some link rates, you absolute icon π
ππ¦πΈππ₯π
π¦ 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