All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>,
	Christoph Hellwig <hch@infradead.org>
Cc: lsf@lists.linux-foundation.org, Tom Herbert <tom@herbertland.com>,
	Brenden Blanco <bblanco@plumgrid.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-mm <linux-mm@kvack.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Jesper Dangaard Brouer <brouer@redhat.com>,
	lsf-pc@lists.linux-foundation.org,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>
Subject: Re: [Lsf-pc] [Lsf] [LSF/MM TOPIC] Generic page-pool recycle facility?
Date: Thu, 07 Apr 2016 12:14:00 -0400	[thread overview]
Message-ID: <1460045640.30063.3.camel@redhat.com> (raw)
In-Reply-To: <2816CC0C-686E-43CA-8689-027085255703@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 655 bytes --]

On Thu, 2016-04-07 at 08:48 -0700, Chuck Lever wrote:
> > 
> > On Apr 7, 2016, at 7:38 AM, Christoph Hellwig <hch@infradead.org>
> > wrote:
> > 
> > This is also very interesting for storage targets, which face the
> > same
> > issue.  SCST has a mode where it caches some fully constructed
> > SGLs,
> > which is probably very similar to what NICs want to do.
> +1 for NFS server.

I have swapped around my slot (into the MM track)
with Jesper's slot (now a plenary session), since
there seems to be a fair amount of interest in
Jesper's proposal from IO and FS people, and my
topic is more MM specific.

-- 
All Rights Reversed.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-04-07 16:14 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1460034425.20949.7.camel@HansenPartnership.com>
2016-04-07 14:17 ` [LSF/MM TOPIC] Generic page-pool recycle facility? Jesper Dangaard Brouer
2016-04-07 14:38   ` [Lsf-pc] " Christoph Hellwig
2016-04-07 15:11     ` [Lsf] " Bart Van Assche
2016-04-10 18:45       ` Sagi Grimberg
2016-04-11 21:41         ` Jesper Dangaard Brouer
2016-04-11 22:02           ` Alexander Duyck
2016-04-11 22:02             ` Alexander Duyck
2016-04-12  6:28             ` Jesper Dangaard Brouer
2016-04-12 15:37               ` Alexander Duyck
2016-04-12 15:37                 ` Alexander Duyck
2016-04-11 22:21           ` Alexei Starovoitov
2016-04-12  6:16             ` Jesper Dangaard Brouer
2016-04-12 17:20               ` Alexei Starovoitov
2016-04-07 15:48     ` Chuck Lever
2016-04-07 16:14       ` Rik van Riel [this message]
2016-04-07 19:43         ` Jesper Dangaard Brouer
2016-04-07 15:18   ` Eric Dumazet
2016-04-07 15:18     ` Eric Dumazet
2016-04-09  9:11     ` [Lsf] " Jesper Dangaard Brouer
2016-04-09 12:34       ` Eric Dumazet
2016-04-11 20:23         ` Jesper Dangaard Brouer
2016-04-11 21:27           ` Eric Dumazet
2016-04-11 21:27             ` Eric Dumazet
2016-04-07 19:48   ` Waskiewicz, PJ
2016-04-07 19:48     ` Waskiewicz, PJ
2016-04-07 20:38     ` Jesper Dangaard Brouer
2016-04-08 16:12       ` Alexander Duyck
2016-04-11  8:58   ` [Lsf-pc] " Mel Gorman
2016-04-11 12:26     ` Jesper Dangaard Brouer
2016-04-11 13:08       ` Mel Gorman
2016-04-11 16:19         ` [Lsf] " Jesper Dangaard Brouer
2016-04-11 16:19           ` Jesper Dangaard Brouer
2016-04-11 16:53           ` Eric Dumazet
2016-04-11 19:47             ` Jesper Dangaard Brouer
2016-04-11 21:14               ` Eric Dumazet
2016-04-11 18:07           ` Mel Gorman
2016-04-11 19:26             ` Jesper Dangaard Brouer
2016-04-11 16:20         ` Matthew Wilcox
2016-04-11 17:46           ` Thadeu Lima de Souza Cascardo
2016-04-11 17:46             ` Thadeu Lima de Souza Cascardo
2016-04-11 18:37             ` Jesper Dangaard Brouer
2016-04-11 18:37               ` Jesper Dangaard Brouer
2016-04-11 18:53               ` Bart Van Assche

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=1460045640.30063.3.camel@redhat.com \
    --to=riel@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bblanco@plumgrid.com \
    --cc=brouer@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=lsf@lists.linux-foundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=tom@herbertland.com \
    /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.