From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>
Cc: Karol Wachowski <karol.wachowski@linux.intel.com>,
Oded Gabbay <ogabbay@kernel.org>,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 5/5] accel/ivpu: Mark 64 kB contiguous areas as contiguous in PTEs
Date: Thu, 8 Jun 2023 07:59:22 +0200 [thread overview]
Message-ID: <20230608055922.GE324119@linux.intel.com> (raw)
In-Reply-To: <71225f48-c1fc-9aef-2ef9-94e2ca5b1ab6@quicinc.com>
On Thu, May 18, 2023 at 08:17:02AM -0600, Jeffrey Hugo wrote:
> On 5/18/2023 7:16 AM, Stanislaw Gruszka wrote:
> > From: Karol Wachowski <karol.wachowski@linux.intel.com>
> >
> > Whenever KMD maps region larger than 64kB that is both aligned and
> > contiguous, set contiguous bit (52) in MMU PTE descriptor for each page
> > in that region.
> >
> > This allows to treat 16 contiguous pages as one and reduce
> > number of MMU page walks required what results in lower latency.
>
> what -> which
Fixed this and applied the set to drm-misc-next
Thanks
Stanislaw
prev parent reply other threads:[~2023-06-08 5:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 13:16 [PATCH 0/5] accel/ivpu: Update MMU code Stanislaw Gruszka
2023-05-18 13:16 ` [PATCH 1/5] accel/ivpu: Remove configuration of MMU TBU1 and TBU3 Stanislaw Gruszka
2023-05-18 13:54 ` Jeffrey Hugo
2023-05-18 13:16 ` [PATCH 2/5] accel/ivpu: Add MMU support for 4 level page mappings Stanislaw Gruszka
2023-05-18 14:04 ` Jeffrey Hugo
2023-05-18 13:16 ` [PATCH 3/5] accel/ivpu: Make DMA bit mask HW specific Stanislaw Gruszka
2023-05-18 14:06 ` Jeffrey Hugo
2023-05-18 13:16 ` [PATCH 4/5] accel/ivpu: Rename and cleanup MMU600 page tables Stanislaw Gruszka
2023-05-18 14:11 ` Jeffrey Hugo
2023-05-18 13:16 ` [PATCH 5/5] accel/ivpu: Mark 64 kB contiguous areas as contiguous in PTEs Stanislaw Gruszka
2023-05-18 14:17 ` Jeffrey Hugo
2023-06-08 5:59 ` Stanislaw Gruszka [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=20230608055922.GE324119@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=karol.wachowski@linux.intel.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
/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.