[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150817.222620.475853456939322841.davem@davemloft.net>
Date: Mon, 17 Aug 2015 22:26:20 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: noamc@...hip.com
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
Alexey.Brodkin@...opsys.com, vgupta@...opsys.com, talz@...hip.com
Subject: Re: [v1 0/6] *** nps_enet fixups ***
From: Noam Camus <noamc@...hip.com>
Date: Tue, 18 Aug 2015 05:04:20 +0000
> I followed "Hardware Architecture" section from:
> http://www.linuxfoundation.org/collaborate/workgroups/networking/napi
> and came up with "reduce processing latency" idea.
That document has lots of incorrect advice, that's for sure.
For one thing, it also says to count TX work against the budget, you
absolutely should not do this. TX work is "free" compared to RX work
(which is several orders of magnitude more expensive) and therefore
should not count against the NAPI budget value.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists