[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7a879d64-1d5a-ebda-8f44-b8d6bdd94afd@itcare.pl>
Date: Mon, 12 Nov 2018 18:06:01 +0100
From: Paweł Staszewski <pstaszewski@...are.pl>
To: Eric Dumazet <eric.dumazet@...il.com>,
Alexander Duyck <alexander.duyck@...il.com>
Cc: aaron.lu@...el.com, linux-mm <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Netdev <netdev@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Jesper Dangaard Brouer <brouer@...hat.com>,
Tariq Toukan <tariqt@...lanox.com>,
ilias.apalodimas@...aro.org, yoel@...knet.dk,
Mel Gorman <mgorman@...hsingularity.net>,
Saeed Mahameed <saeedm@...lanox.com>,
Michal Hocko <mhocko@...e.com>,
Vlastimil Babka <vbabka@...e.cz>, dave.hansen@...ux.intel.com
Subject: Re: [PATCH 1/2] mm/page_alloc: free order-0 pages through PCP in
page_frag_free()
W dniu 12.11.2018 o 16:44, Eric Dumazet pisze:
>
> On 11/12/2018 07:30 AM, Alexander Duyck wrote:
>
>> It sounds to me like XDP would probably be your best bet. With that
>> you could probably get away with smaller ring sizes, higher interrupt
>> rates, and get the advantage of it batching the Tx without having to
>> drop packets.
> Add to this that with XDP (or anything lowering per packet processing costs)
> you can reduce number of cpus/queues, get better latencies, and bigger TX batches.
Yes for sure - the best for my use case will be to implement XDP :)
But for real life not test lab use programs like xdp_fwd need to be
extended for minimal information needed from IP router - like counters
and some aditional debug for traffic like sniffing / sampling for ddos
detection.
And that is rly minimum needed - for routing IP traffic with XDP
Powered by blists - more mailing lists