From: "Paweł Staszewski" <pstaszewski@itcare.pl>
To: Eric Dumazet <eric.dumazet@gmail.com>,
Alexander Duyck <alexander.duyck@gmail.com>
Cc: aaron.lu@intel.com, linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jesper Dangaard Brouer <brouer@redhat.com>,
Tariq Toukan <tariqt@mellanox.com>,
ilias.apalodimas@linaro.org, yoel@kviknet.dk,
Mel Gorman <mgorman@techsingularity.net>,
Saeed Mahameed <saeedm@mellanox.com>,
Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
dave.hansen@linux.intel.com
Subject: Re: [PATCH 1/2] mm/page_alloc: free order-0 pages through PCP in page_frag_free()
Date: Mon, 12 Nov 2018 18:06:01 +0100 [thread overview]
Message-ID: <7a879d64-1d5a-ebda-8f44-b8d6bdd94afd@itcare.pl> (raw)
In-Reply-To: <6edcec1a-eefa-7861-1af4-cdf7fa45184c@gmail.com>
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
next prev parent reply other threads:[~2018-11-12 17:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 8:58 [PATCH 1/2] mm/page_alloc: free order-0 pages through PCP in page_frag_free() Aaron Lu
2018-11-05 8:58 ` [PATCH 2/2] mm/page_alloc: use a single function to free page Aaron Lu
2018-11-05 16:39 ` Dave Hansen
2018-11-06 5:30 ` [PATCH v2 " Aaron Lu
2018-11-06 8:16 ` Vlastimil Babka
2018-11-06 8:47 ` Aaron Lu
2018-11-06 9:32 ` Vlastimil Babka
2018-11-06 11:20 ` Aaron Lu
2018-11-06 11:31 ` [PATCH v3 " Aaron Lu
2018-11-06 12:06 ` Vlastimil Babka
2018-11-05 9:26 ` [PATCH 1/2] mm/page_alloc: free order-0 pages through PCP in page_frag_free() Vlastimil Babka
2018-11-05 9:26 ` Mel Gorman
2018-11-05 9:55 ` Jesper Dangaard Brouer
2018-11-05 10:46 ` Ilias Apalodimas
2018-11-05 15:44 ` Alexander Duyck
2018-11-10 23:54 ` Paweł Staszewski
2018-11-11 23:05 ` Alexander Duyck
2018-11-12 0:39 ` Paweł Staszewski
2018-11-12 15:30 ` Alexander Duyck
2018-11-12 15:44 ` Eric Dumazet
2018-11-12 17:06 ` Paweł Staszewski [this message]
2018-11-12 17:01 ` Paweł Staszewski
2018-11-05 16:37 ` Dave Hansen
2018-11-06 5:28 ` [PATCH v2 " Aaron Lu
2018-11-07 9:59 ` Tariq Toukan
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=7a879d64-1d5a-ebda-8f44-b8d6bdd94afd@itcare.pl \
--to=pstaszewski@itcare.pl \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=brouer@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=eric.dumazet@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=tariqt@mellanox.com \
--cc=vbabka@suse.cz \
--cc=yoel@kviknet.dk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).