From: "Stephen Bates" <sbates@raithlin.com>
To: Jason Gunthorpe <jgg@mellanox.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Alex Rosenbaum" <alexr@mellanox.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Christian König" <christian.koenig@amd.com>,
"Christoph Hellwig" <hch@lst.de>,
"Christopher Lameter" <cl@linux.com>,
"Dan Williams" <dan.j.williams@intel.com>,
"Don Dutile" <ddutile@redhat.com>,
"Doug Ledford" <dledford@redhat.com>, "Jan Kara" <jack@suse.cz>,
"John Hubbard" <jhubbard@nvidia.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Logan Gunthorpe" <logang@deltatee.com>,
"Matthew Wilcox" <willy@infradead.org>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Noa Osherovich" <noaos@mellanox.com>,
"Parav Pandit" <parav@mellanox.com>
Subject: Re: Linux RDMA mini-conf at Plumbers 2018
Date: Mon, 1 Oct 2018 15:17:49 +0000 [thread overview]
Message-ID: <0EFD8B7D-15C2-4314-B099-B7621AECFC4C@raithlin.com> (raw)
In-Reply-To: <20180920181923.GA6542@mellanox.com>
Hi Jason and Leon
> This year we expect to have close to a day set aside for RDMA related
> topics. Including up to half a day for the thorny general kernel issues
> related to get_user_pages(), particularly as exasperated by RDMA.
Looks like a great set of topics.
> RDMA and PCI peer to peer
I will happily be a leader/organizer for this section and can provide an
overview of p2pdma to get the ball rolling.
Cheers
Stephen
prev parent reply other threads:[~2018-10-01 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 18:19 Jason Gunthorpe
2018-09-20 18:54 ` Leon Romanovsky
2018-09-23 15:17 ` Mike Rapoport
2018-10-01 15:17 ` Stephen Bates [this message]
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=0EFD8B7D-15C2-4314-B099-B7621AECFC4C@raithlin.com \
--to=sbates@raithlin.com \
--cc=alex.williamson@redhat.com \
--cc=alexr@mellanox.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=cl@linux.com \
--cc=dan.j.williams@intel.com \
--cc=ddutile@redhat.com \
--cc=dledford@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jgg@mellanox.com \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=noaos@mellanox.com \
--cc=npiggin@gmail.com \
--cc=parav@mellanox.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox