From: Mel Gorman <mgorman@suse.de>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Linux-MM <linux-mm@kvack.org>,
Linux-Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>, Neil Brown <neilb@suse.de>
Subject: Re: [PATCH 00/13] Swap-over-NBD without deadlocking
Date: Tue, 26 Apr 2011 15:46:35 +0100 [thread overview]
Message-ID: <20110426144635.GK4658@suse.de> (raw)
In-Reply-To: <1303827785.20212.266.camel@twins>
On Tue, Apr 26, 2011 at 04:23:05PM +0200, Peter Zijlstra wrote:
> On Tue, 2011-04-26 at 08:36 +0100, Mel Gorman wrote:
> > Comments?
>
> Last time I brought up the whole swap over network bits I was pointed
> towards the generic skb recycling work:
>
> http://lwn.net/Articles/332037/
>
> as a means to pre-allocate memory,
I'd taken note of this to take a much closer look if it turned
out reservations were necessary and to find out what happened with
these patches. So far, bigger reservations have *not* been required
but I agree recycling SKBs may be a better alternative than large
reservations or preallocations if they are necessary.
> and it was suggested to simply pin
> the few route-cache entries required to route these packets and
> dis-allow swap packets to be fragmented (these last two avoid lots of
> funny allocation cases in the network stack).
>
I did find that only a few route-cache entries should be required. In
the original patches I worked with, there was a reservation for the
maximum possible number of route-cache entries. I thought this was
overkill and instead reserved 1-per-active-swapfile-backed-by-NFS.
--
Mel Gorman
SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@suse.de>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Linux-MM <linux-mm@kvack.org>,
Linux-Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
David Miller <davem@davemloft.net>, Neil Brown <neilb@suse.de>
Subject: Re: [PATCH 00/13] Swap-over-NBD without deadlocking
Date: Tue, 26 Apr 2011 15:46:35 +0100 [thread overview]
Message-ID: <20110426144635.GK4658@suse.de> (raw)
In-Reply-To: <1303827785.20212.266.camel@twins>
On Tue, Apr 26, 2011 at 04:23:05PM +0200, Peter Zijlstra wrote:
> On Tue, 2011-04-26 at 08:36 +0100, Mel Gorman wrote:
> > Comments?
>
> Last time I brought up the whole swap over network bits I was pointed
> towards the generic skb recycling work:
>
> http://lwn.net/Articles/332037/
>
> as a means to pre-allocate memory,
I'd taken note of this to take a much closer look if it turned
out reservations were necessary and to find out what happened with
these patches. So far, bigger reservations have *not* been required
but I agree recycling SKBs may be a better alternative than large
reservations or preallocations if they are necessary.
> and it was suggested to simply pin
> the few route-cache entries required to route these packets and
> dis-allow swap packets to be fragmented (these last two avoid lots of
> funny allocation cases in the network stack).
>
I did find that only a few route-cache entries should be required. In
the original patches I worked with, there was a reservation for the
maximum possible number of route-cache entries. I thought this was
overkill and instead reserved 1-per-active-swapfile-backed-by-NFS.
--
Mel Gorman
SUSE Labs
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-04-26 14:46 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 7:36 [PATCH 00/13] Swap-over-NBD without deadlocking Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 7:36 ` [PATCH 01/13] mm: Serialize access to min_free_kbytes Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 7:36 ` [PATCH 02/13] mm: sl[au]b: Add knowledge of PFMEMALLOC reserve pages Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 11:15 ` NeilBrown
2011-04-26 11:15 ` NeilBrown
2011-04-26 11:33 ` Mel Gorman
2011-04-26 11:33 ` Mel Gorman
2011-04-26 12:05 ` NeilBrown
2011-04-26 12:05 ` NeilBrown
2011-04-26 11:37 ` NeilBrown
2011-04-26 11:37 ` NeilBrown
2011-04-26 13:59 ` Mel Gorman
2011-04-26 13:59 ` Mel Gorman
2011-04-27 23:21 ` NeilBrown
2011-04-27 23:21 ` NeilBrown
2011-04-28 9:46 ` Mel Gorman
2011-04-28 9:46 ` Mel Gorman
2011-04-26 7:36 ` [PATCH 03/13] mm: Introduce __GFP_MEMALLOC to allow access to emergency reserves Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 9:49 ` NeilBrown
2011-04-26 9:49 ` NeilBrown
2011-04-26 10:36 ` Mel Gorman
2011-04-26 10:36 ` Mel Gorman
2011-04-26 10:53 ` NeilBrown
2011-04-26 10:53 ` NeilBrown
2011-04-26 14:00 ` Mel Gorman
2011-04-26 14:00 ` Mel Gorman
2011-04-26 7:36 ` [PATCH 04/13] mm: allow PF_MEMALLOC from softirq context Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 7:36 ` [PATCH 05/13] mm: Ignore mempolicies when using ALLOC_NO_WATERMARK Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 7:36 ` [PATCH 06/13] net: Introduce sk_allocation() to allow addition of GFP flags depending on the individual socket Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 7:36 ` [PATCH 07/13] netvm: Allow the use of __GFP_MEMALLOC by specific sockets Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 7:36 ` [PATCH 08/13] netvm: Allow skb allocation to use PFMEMALLOC reserves Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 7:36 ` [PATCH 09/13] netvm: Set PF_MEMALLOC as appropriate during SKB processing Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 12:21 ` NeilBrown
2011-04-26 12:21 ` NeilBrown
2011-04-26 14:10 ` Mel Gorman
2011-04-26 14:10 ` Mel Gorman
2011-04-26 23:22 ` NeilBrown
2011-04-26 23:22 ` NeilBrown
2011-04-26 7:36 ` [PATCH 10/13] mm: Micro-optimise slab to avoid a function call Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 7:36 ` [PATCH 11/13] nbd: Set SOCK_MEMALLOC for access to PFMEMALLOC reserves Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 7:36 ` [PATCH 12/13] mm: Throttle direct reclaimers if PF_MEMALLOC reserves are low and swap is backed by network storage Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 12:30 ` NeilBrown
2011-04-26 12:30 ` NeilBrown
2011-04-26 14:26 ` Mel Gorman
2011-04-26 14:26 ` Mel Gorman
2011-04-26 23:18 ` NeilBrown
2011-04-26 23:18 ` NeilBrown
2011-04-27 8:36 ` Mel Gorman
2011-04-27 8:36 ` Mel Gorman
2011-04-26 7:36 ` [PATCH 13/13] mm: Account for the number of times direct reclaimers get throttled Mel Gorman
2011-04-26 7:36 ` Mel Gorman
2011-04-26 12:35 ` NeilBrown
2011-04-26 12:35 ` NeilBrown
2011-04-26 14:26 ` Mel Gorman
2011-04-26 14:26 ` Mel Gorman
2011-04-26 14:23 ` [PATCH 00/13] Swap-over-NBD without deadlocking Peter Zijlstra
2011-04-26 14:23 ` Peter Zijlstra
2011-04-26 14:46 ` Mel Gorman [this message]
2011-04-26 14:46 ` Mel Gorman
2011-04-26 14:50 ` Peter Zijlstra
2011-04-26 14:50 ` Peter Zijlstra
2011-04-27 8:43 ` Mel Gorman
2011-04-27 8:43 ` Mel Gorman
2011-04-28 13:31 ` Pavel Machek
2011-04-28 13:31 ` Pavel Machek
2011-04-28 13:42 ` Mel Gorman
2011-04-28 13:42 ` Mel Gorman
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=20110426144635.GK4658@suse.de \
--to=mgorman@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=neilb@suse.de \
--cc=netdev@vger.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.