From: Rik van Riel <riel@surriel.com>
To: Christopher Lameter <cl@linux.com>, Michal Hocko <mhocko@kernel.org>
Cc: linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org
Subject: Re: [Lsf-pc] Memory management facing a 400Gpbs network link
Date: Thu, 21 Feb 2019 13:24:57 -0500 [thread overview]
Message-ID: <3057d2336e88897309756a9c0e10727856589965.camel@surriel.com> (raw)
In-Reply-To: <010001691144c94b-c935fd1d-9c90-40a5-9763-2c05ef0df7f4-000000@email.amazonses.com>
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
On Thu, 2019-02-21 at 18:15 +0000, Christopher Lameter wrote:
> B) Provide fast memory in the NIC
>
> Since the NIC is at capacity limits when it comes to pushing data
> from the NIC into memory the obvious solution is to not go to main
> memory but provide faster on NIC memory that can then be accessed
> from the host as needed. Now the applications creates I/O
> bottlenecks
> when accessing their data or they need to implement complicated
> transfer mechanisms to retrieve and store data onto the NIC
> memory.
Don't Intel and AMD both have High Bandwidth Memory
available?
Is it possible to place your network buffer in HBM,
and process the data from there?
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-21 18:25 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
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 ` Rik van Riel [this message]
2019-02-21 18:47 ` [Lsf-pc] " 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=3057d2336e88897309756a9c0e10727856589965.camel@surriel.com \
--to=riel@surriel.com \
--cc=cl@linux.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@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.