Thread (10 messages) 10 messages, 5 authors, 2012-10-01

RE: [PATCH net-next] mlx4: use dev_kfree_skb() instead of dev_kfree_skb_any()

From: Eric Dumazet <hidden>
Date: 2012-09-19 12:13:04

On Wed, 2012-09-19 at 07:58 +0000, Yevgeny Petrilin wrote:
quoted
Since commit e22979d96a5 (mlx4_en: Moving to Interrupts for TX
completions), we no longer can free TX skb from hard IRQ, but only from
normal softirq or process context.

Therefore, we can directly call dev_kfree_skb() from
mlx4_en_free_tx_desc() like other conventional NAPI drivers.
Hi Eric,
At the moment the TX completion processing is done from IRQ context.
So I think we need to change the driver to work with NAPI for TX completions
before making this change.

I'll send the patch in a few days.
Oops you're right, it seems I misread e22979d96 commit.

irq term is a bit generic, you might add soft/hard qualifiers to
distinguish the variant.

Thanks
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help