From: Miklos Szeredi <miklos@szeredi.hu>
To: jens.axboe@oracle.com
Cc: miklos@szeredi.hu, torvalds@linux-foundation.org,
akpm@linux-foundation.org, nickpiggin@yahoo.com.au,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [patch v3] splice: fix race with page invalidation
Date: Wed, 30 Jul 2008 22:05:58 +0200 [thread overview]
Message-ID: <E1KOHvq-0001oX-OW@pomaz-ex.szeredi.hu> (raw)
In-Reply-To: <20080730194516.GO20055@kernel.dk> (message from Jens Axboe on Wed, 30 Jul 2008 21:45:16 +0200)
On Wed, 30 Jul 2008, Jens Axboe wrote:
> On Wed, Jul 30 2008, Miklos Szeredi wrote:
> > > On Wed, 30 Jul 2008, Jens Axboe wrote:
> > > > You snipped the part where Linus objected to dismissing the async
> > > > nature, I fully agree with that part.
> >
> > And also note in what Nick said in the referenced mail: it would be
> > nice if someone actually _cared_ about the async nature. The fact
> > that it has been broken from the start, and nobody noticed is a strong
> > hint that currently there isn't anybody who does.
>
> That's largely due to the (still) lack of direct splice users. It's a
> clear part of the design and benefit of using splice. I very much care
> about this, and as soon as there are available cycles for this, I'll get
> it into better shape in this respect. Taking a step backwards is not the
> right way forward, imho.
So what is? The only way forward is to put those cycles into it,
which nobody seems to have available.
Take this patch as a bugfix. It's not in any way showing the way
forward: as soon as you have the time, you can revert it and start
from the current state.
Hmm?
Miklos
--
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>
next prev parent reply other threads:[~2008-07-30 20:05 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 9:43 Miklos Szeredi
2008-07-30 17:00 ` Linus Torvalds
2008-07-30 17:29 ` Miklos Szeredi
2008-07-30 17:54 ` Jens Axboe
2008-07-30 18:32 ` Miklos Szeredi
2008-07-30 18:43 ` Miklos Szeredi
2008-07-30 19:45 ` Jens Axboe
2008-07-30 20:05 ` Miklos Szeredi [this message]
2008-07-30 20:13 ` Linus Torvalds
2008-07-30 20:45 ` Miklos Szeredi
2008-07-30 20:51 ` Linus Torvalds
2008-07-30 21:16 ` Miklos Szeredi
2008-07-30 21:22 ` Linus Torvalds
2008-07-30 21:46 ` Miklos Szeredi
2008-07-30 21:56 ` Linus Torvalds
2008-07-31 0:11 ` Jamie Lokier
2008-07-31 0:42 ` Jamie Lokier
2008-07-31 0:51 ` Linus Torvalds
2008-07-31 0:54 ` Linus Torvalds
2008-07-31 6:12 ` Jamie Lokier
2008-07-31 10:26 ` Evgeniy Polyakov
2008-07-31 12:33 ` Jamie Lokier
2008-07-31 12:49 ` Nick Piggin
2008-07-31 13:29 ` Evgeniy Polyakov
2008-07-31 16:56 ` Linus Torvalds
2008-07-31 16:34 ` Linus Torvalds
2008-07-31 17:21 ` Jamie Lokier
2008-07-31 18:54 ` Linus Torvalds
2008-07-31 7:30 ` Miklos Szeredi
2008-07-31 2:16 ` Nick Piggin
2008-07-31 12:59 ` Nick Piggin
2008-07-31 17:00 ` Linus Torvalds
2008-07-31 18:13 ` Miklos Szeredi
2008-08-01 1:22 ` Nick Piggin
2008-08-01 18:28 ` Miklos Szeredi
2008-08-01 18:32 ` Linus Torvalds
2008-08-02 4:26 ` Nick Piggin
2008-08-04 15:29 ` Jamie Lokier
2008-08-05 2:57 ` Nick Piggin
2008-08-11 3:22 ` Michael Kerrisk
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=E1KOHvq-0001oX-OW@pomaz-ex.szeredi.hu \
--to=miklos@szeredi.hu \
--cc=akpm@linux-foundation.org \
--cc=jens.axboe@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--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