All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Christoph Hellwig <hch@infradead.org>,
	Jesper Dangaard Brouer <brouer@redhat.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Tom Herbert <tom@herbertland.com>,
	Brenden Blanco <bblanco@plumgrid.com>,
	"lsf@lists.linux-foundation.org" <lsf@lists.linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	Alexei Starovoitov <alexei.starovoitov@gmail.com>
Subject: Re: [Lsf] [Lsf-pc] [LSF/MM TOPIC] Generic page-pool recycle facility?
Date: Thu, 7 Apr 2016 08:11:51 -0700	[thread overview]
Message-ID: <570678B7.7010802@sandisk.com> (raw)
In-Reply-To: <20160407143854.GA7685@infradead.org>

On 04/07/16 07:38, Christoph Hellwig 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.

I think a cached allocator for page sets + the scatterlists that 
describe these page sets would not only be useful for SCSI target 
implementations but also for the Linux SCSI initiator. Today the scsi-mq 
code reserves space in each scsi_cmnd for a scatterlist of 
SCSI_MAX_SG_SEGMENTS. If scatterlists would be cached together with page 
sets less memory would be needed per scsi_cmnd. See also 
scsi_mq_setup_tags() and scsi_alloc_sgtable().

Bart.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-04-07 15:11 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     ` Bart Van Assche [this message]
2016-04-10 18:45       ` [Lsf] " 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       ` [Lsf-pc] [Lsf] " Rik van Riel
2016-04-07 19:43         ` [Lsf] [Lsf-pc] " 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=570678B7.7010802@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bblanco@plumgrid.com \
    --cc=brouer@redhat.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.