From: Michal Hocko <mhocko@kernel.org>
To: Christopher Lameter <cl@linux.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: Memory management facing a 400Gpbs network link
Date: Tue, 19 Feb 2019 13:26:09 +0100 [thread overview]
Message-ID: <20190219122609.GN4525@dhcp22.suse.cz> (raw)
In-Reply-To: <01000168e2f54113-485312aa-7e08-4963-af92-803f8c7d21e6-000000@email.amazonses.com>
On Tue 12-02-19 18:25:50, Cristopher Lameter wrote:
> 400G Infiniband will become available this year. This means that the data
> ingest speeds can be higher than the bandwidth of the processor
> interacting with its own memory.
>
> For example a single hardware thread is limited to 20Gbyte/sec whereas the
> network interface provides 50Gbytes/sec. These rates can only be obtained
> currently with pinned memory.
>
> How can we evolve the memory management subsystem to operate at higher
> speeds with more the comforts of paging and system calls that we are used
> to?
Realistically, is there anything we _can_ do when the HW is the
bottleneck?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-02-19 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 18:25 Memory management facing a 400Gpbs network link Christopher Lameter
2019-02-15 16:34 ` Jerome Glisse
2019-02-19 12:26 ` Michal Hocko [this message]
2019-02-19 14:21 ` Christopher Lameter
2019-02-19 17:36 ` Michal Hocko
2019-02-19 18:21 ` Christopher Lameter
2019-02-19 18:42 ` Alexander Duyck
2019-02-19 19:13 ` Michal Hocko
2019-02-19 20:46 ` Christopher Lameter
2019-02-20 8:31 ` Michal Hocko
2019-02-21 18:15 ` Christopher Lameter
2019-02-21 18:24 ` [Lsf-pc] " Rik van Riel
2019-02-21 18:47 ` Christopher Lameter
2019-02-21 20:13 ` Jerome Glisse
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=20190219122609.GN4525@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=cl@linux.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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.