From: Daniel Borkmann <dborkman@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, brouer@redhat.com
Subject: Re: [PATCH net-next] packet: respect devices with LLTX flag in direct xmit
Date: Fri, 28 Mar 2014 22:13:40 +0100 [thread overview]
Message-ID: <5335E604.4020105@redhat.com> (raw)
In-Reply-To: <20140328.165058.1610297081920676758.davem@davemloft.net>
On 03/28/2014 09:50 PM, David Miller wrote:
> From: Daniel Borkmann <dborkman@redhat.com>
> Date: Thu, 27 Mar 2014 16:38:30 +0100
>
>> Quite often it can be useful to test with dummy or similar
>> devices as a blackhole sink for skbs. Such devices are only
>> equipped with a single txq, but marked as NETIF_F_LLTX as
>> they do not require locking their internal queues on xmit
>> (or implement locking themselves). Therefore, rather use
>> HARD_TX_{UN,}LOCK API, so that NETIF_F_LLTX will be respected.
>>
>> trafgen mmap/TX_RING example against dummy device with config
>> foo: { fill(0xff, 64) } results in the following performance
>> improvements for such scenarios on an ordinary Core i7/2.80GHz:
> ...
>> Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
>> Cc: Jesper Dangaard Brouer <brouer@redhat.com>
>
> Applied, nice work.
>
> The only remaining issue is that Eric seems to suggest that a tx
> dropped counter bump should be added. Please submit that as a
> follow-on if my reading of his feedback is accurate.
Yes, will do next week. I think at time of submission we didn't
have that yet. :)
next prev parent reply other threads:[~2014-03-28 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 15:38 [PATCH net-next] packet: respect devices with LLTX flag in direct xmit Daniel Borkmann
2014-03-27 16:01 ` Eric Dumazet
2014-03-27 16:04 ` Eric Dumazet
2014-03-28 20:50 ` David Miller
2014-03-28 21:13 ` Daniel Borkmann [this message]
2014-03-29 15:02 ` Eric Dumazet
2014-03-30 21:52 ` Daniel Borkmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5335E604.4020105@redhat.com \
--to=dborkman@redhat.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.