From: "Volkin, Bradley D" <bradley.d.volkin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/i915: Process page flags once rather than per pwrite/pread
Date: Fri, 7 Mar 2014 10:14:24 -0800 [thread overview]
Message-ID: <20140307181424.GA7286@bdvolkin-ubuntu-desktop> (raw)
In-Reply-To: <1394181037-30480-1-git-send-email-chris@chris-wilson.co.uk>
Reviewed-by: Brad Volkin <bradley.d.volkin@intel.com>
On Fri, Mar 07, 2014 at 12:30:36AM -0800, Chris Wilson wrote:
> We used to lock individual pages inside the buffer object and so needed
> to update the page flags every time. However, we now pin the pages into
> the object for the duration of the pwrite/pread (and hopefully much
> longer) and so we can forgo the flag updates until we release all the
> pages.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 9 ++-------
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index ba7dc4868066..877afb2c576d 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -627,12 +627,10 @@ i915_gem_shmem_pread(struct drm_device *dev,
>
> mutex_lock(&dev->struct_mutex);
>
> -next_page:
> - mark_page_accessed(page);
> -
> if (ret)
> goto out;
>
> +next_page:
> remain -= page_length;
> user_data += page_length;
> offset += page_length;
> @@ -950,13 +948,10 @@ i915_gem_shmem_pwrite(struct drm_device *dev,
>
> mutex_lock(&dev->struct_mutex);
>
> -next_page:
> - set_page_dirty(page);
> - mark_page_accessed(page);
> -
> if (ret)
> goto out;
>
> +next_page:
> remain -= page_length;
> user_data += page_length;
> offset += page_length;
> --
> 1.9.0
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2014-03-07 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 8:30 [PATCH 1/2] drm/i915: Process page flags once rather than per pwrite/pread Chris Wilson
2014-03-07 8:30 ` [PATCH 2/2] drm/i915: Do not force non-caching copies for pwrite along shmem path Chris Wilson
2014-03-07 8:39 ` Daniel Vetter
2014-03-07 9:50 ` Chris Wilson
2014-03-07 18:14 ` Volkin, Bradley D
2014-03-07 23:03 ` Daniel Vetter
2014-03-07 18:14 ` Volkin, Bradley D [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=20140307181424.GA7286@bdvolkin-ubuntu-desktop \
--to=bradley.d.volkin@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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