All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Khlebnikov <khlebnikov@openvz.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Hugh Dickins <hughd@google.com>,
	linux-kernel@vger.kernel.org, Mel Gorman <mgorman@suse.de>,
	Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] mm/swap: add independed bio pool for swap
Date: Thu, 20 Dec 2012 13:29:35 +0400	[thread overview]
Message-ID: <50D2DA7F.3030902@openvz.org> (raw)
In-Reply-To: <20121219165343.ccb3a956.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Mon, 17 Dec 2012 20:45:13 -0800 (PST)
> Hugh Dickins<hughd@google.com>  wrote:
>
>> On Fri, 14 Dec 2012, Konstantin Khlebnikov wrote:
>>
>>> This bio pool guarantees reclaiming progress for anonymous pages.
>>> All avaliable bio in fs_bio_set may be borrowed by writeback which may
>>> never ends, because disk too slow or broken. I have seen this situation in
>>> real life in system where was a lot of bio requests to a loop device which
>>> laying on top of special fuse-based filesystem.
>>
>> Hmm, perhaps, I'm not at all sure.
>
> It probably maybe perhaps makes sense.  Of course, you're screwed if
> one of your swap devices is "disk too slow or broken".
>
> My crystal ball tells me that the 2015 kernel will have a bioset per
> physical device...
>

I predict that they also will be per-cpu. Well... probably maybe we should
just wait for this shining future. I leave this to your discretion...

      reply	other threads:[~2012-12-20  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14 11:01 [PATCH] mm/swap: add independed bio pool for swap Konstantin Khlebnikov
2012-12-18  4:45 ` Hugh Dickins
2012-12-20  0:53   ` Andrew Morton
2012-12-20  9:29     ` Konstantin Khlebnikov [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=50D2DA7F.3030902@openvz.org \
    --to=khlebnikov@openvz.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    /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.