Skip to content
Draft
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions src/include/zf_internal/tx_send.h
Original file line number Diff line number Diff line change
Expand Up @@ -288,6 +288,7 @@ zf_send(struct zf_tx* restrict tx,
}
}
zf_assert_nequal(vi->nic_type.arch, EF_VI_ARCH_EFCT);
zf_assert_nequal(vi->nic_type.arch, EF_VI_ARCH_EF10CT);
Comment on lines 290 to +291
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assert that CTPIO_ONLY capability wasn't set?

/* Strictly speaking, we should call ef_vi_transmit_ctpio_fallback()
* to post a CTPIO fallback descriptor. However, that entry point is
* actually identical to this one, and this code path is also used
Expand Down
3 changes: 2 additions & 1 deletion src/lib/zf/tx_warm.c
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,8 @@ int enable_tx_warm(struct zf_tx* tx, zf_tx_warm_state* state)
zf_log_stack_trace(st, "%s: TX warm enabled\n", __func__);
char* ctpio_warm_buf = NULL;
state->ctpio_warm_buf_id = PKT_INVALID;
if( vi->vi_flags & EF_VI_TX_CTPIO && vi->nic_type.arch != EF_VI_ARCH_EFCT ) {
if( vi->vi_flags & EF_VI_TX_CTPIO && vi->nic_type.arch != EF_VI_ARCH_EFCT
&& vi->nic_type.arch != EF_VI_ARCH_EF10CT ) {
Comment on lines +19 to +20
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The check here is on whether we need to post a dma fallback, which we don't if we have the CTPIO_ONLY capability, so I think that's what we should use.

int rc = zft_alloc_pkt(&st->pool, &state->ctpio_warm_buf_id);
if( rc < 0 )
return rc;
Expand Down
Loading