From: Jens Axboe <axboe@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@digeo.com
Subject: Re: [patch][cft] zero-copy dma cd writing and ripping
Date: Mon, 28 Oct 2002 17:18:57 +0100 [thread overview]
Message-ID: <20021028161857.GK2937@suse.de> (raw)
In-Reply-To: <1035822310.8970.9.camel@rth.ninka.net>
On Mon, Oct 28 2002, David S. Miller wrote:
> On Mon, 2002-10-28 at 07:54, Jens Axboe wrote:
> > I agree then. I will remove references to flush_dcache_page() in
> > bio_map_user() and bio_unmap_user(), and we'll just unconditionally do
> > flush_dcache_page() on every page mapped in get_user_pages(). That
> > sounds far better to me. Do you really expect users of get_user_pages()
> > to get this right (remember, we are often talking about device drivers
> > :-). I sure am not :)
>
> I have no expectations whatsoever :-)
> I totally agree with you.
Good, so it shall be then :-)
A related question. get_user_pages() does page_cache_get() on the page,
except if it's reserved. First question is 'why' doesn't it do that on a
reserved page? We get this conditional when mapping, and the unmapping
needs to check for reserved as well before doing page_cache_release().
Surely the extra reference would be ok to hold for PageReserved pages
as well?
And it not, there's a bug if get_user_pages() fails:
if (!PageReserved(pages[i]))
page_cache_get(pages[i]);
and if we ever fail:
while (i--)
page_cache_release(pages[i]);
--
Jens Axboe
next prev parent reply other threads:[~2002-10-28 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 15:56 [patch][cft] zero-copy dma cd writing and ripping Jens Axboe
2002-10-28 12:35 ` David S. Miller
2002-10-28 12:42 ` Jens Axboe
2002-10-28 14:40 ` David S. Miller
2002-10-28 14:55 ` Jens Axboe
2002-10-28 15:08 ` Jens Axboe
2002-10-28 16:03 ` David S. Miller
2002-10-28 15:54 ` Jens Axboe
2002-10-28 16:25 ` David S. Miller
2002-10-28 16:18 ` Jens Axboe [this message]
2002-10-29 2:27 ` David S. Miller
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=20021028161857.GK2937@suse.de \
--to=axboe@suse.de \
--cc=akpm@digeo.com \
--cc=davem@redhat.com \
--cc=linux-kernel@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.