From: Jens Axboe <jens.axboe@oracle.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@linux-foundation.org, max@duempel.org,
torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch 2/3] splice: implement default splice_read method
Date: Thu, 14 May 2009 19:29:35 +0200 [thread overview]
Message-ID: <20090514172935.GR4140@kernel.dk> (raw)
In-Reply-To: <E1M4ALP-0005za-1i@pomaz-ex.szeredi.hu>
On Wed, May 13 2009, Miklos Szeredi wrote:
> On Wed, 13 May 2009, Jens Axboe wrote:
> > On Tue, May 12 2009, Andrew Morton wrote:
> > > On Thu, 07 May 2009 15:37:36 +0200 Miklos Szeredi <miklos@szeredi.hu> wrote:
> > >
> > > > + for (i = 0; i < spd.nr_pages; i++) {
> > > > + kunmap(pages[i]);
> > >
> > > It is deadlockable if any thread of control holds more than a single
> > > kmap at a time.
> > >
> > > Because there are a finite number of kmaps available, and if one is
> > > unavailable, kmap() waits for one to become free. If the number of
> > > waiting threads equals the number of available slots, nobody makes any
> > > progress.
>
> Ouch.
>
> >
> > Good catch, that will not work reliably. I've applied the below.
>
> Thanks.
>
> The bigger problem is that the default_file_splice_write()
> implementation in the other patch does the same (it calls
> buf->ops->map() on all buffers).
Yep that's even worse, as that should go BUG() pretty much immediately
when the KM_USER0 slot is reused!
> Hmm. Simple solution would be to do a write() for each buffer. But
> this only affects HIGHMEM kernels, so it's a bit pointless to do that
> on all archs. Sigh...
It is unfortunate, we are going to be stuck with that for some time
still...
--
Jens Axboe
next prev parent reply other threads:[~2009-05-14 17:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 13:37 [patch 0/3] make splice more generic Miklos Szeredi
2009-05-07 13:37 ` [patch 1/3] splice: implement pipe to pipe splicing Miklos Szeredi
2009-05-07 13:37 ` [patch 2/3] splice: implement default splice_read method Miklos Szeredi
2009-05-13 5:35 ` Andrew Morton
2009-05-13 6:37 ` Jens Axboe
2009-05-13 9:01 ` Miklos Szeredi
2009-05-14 17:29 ` Jens Axboe [this message]
2009-05-14 17:54 ` Miklos Szeredi
2009-05-14 18:00 ` Jens Axboe
2009-05-18 12:36 ` Miklos Szeredi
2009-05-19 9:38 ` Jens Axboe
2009-05-07 13:37 ` [patch 3/3] splice: implement default splice_write method Miklos Szeredi
2009-05-07 15:55 ` [patch 0/3] make splice more generic Linus Torvalds
2009-05-11 15:17 ` Miklos Szeredi
2009-05-09 11:36 ` Max Kellermann
2009-05-11 12:12 ` Jens Axboe
2009-05-11 15:22 ` Miklos Szeredi
2009-05-14 20:27 ` Jamie Lokier
2009-05-15 7:32 ` Jens Axboe
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=20090514172935.GR4140@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max@duempel.org \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).