From: "Dave Airlie" <airlied@gmail.com>
To: "Shaohua Li" <shaohua.li@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Arjan van de Ven" <arjan@infradead.org>
Subject: Re: [patch 0/2] reduce agpgart memory allocation time
Date: Mon, 4 Aug 2008 16:53:37 +1000 [thread overview]
Message-ID: <21d7e9970808032353m40fcea6dtbf1b7bc1c5cf06d9@mail.gmail.com> (raw)
In-Reply-To: <1217832677.21811.7.camel@sli10-desk.sh.intel.com>
On Mon, Aug 4, 2008 at 4:51 PM, Shaohua Li <shaohua.li@intel.com> wrote:
> agpgart memory allocation is quite expensive. For each page agpgart
> allocated, it changes the page to uc and as result flush tlb/cache for
> the page. In my test, Intel Xorg driver takes about 0.2s for a 32M 3D
> fb, and the total time for memory allocation is about 0.33s when intel
> xorg driver initializes. Below patches fix the gap. It can reduce the
> time to 0.03s, so xserver can boot 0.3s faster.
>
This approach is quite like what was there before, and I think was
objected to on the grounds the caller might forget to
call the flush and leave the system in an inconsistent state.
Personally I've never bought that argument, its not like we have
thousands of users for this API.
I proposed an alternative interface but I failed to get it merged and
ran out of time
http://www.ussg.iu.edu/hypermail/linux/kernel/0804.3/1112.html
I was trying to get the cpa interface to allow arrays of pages to be
passed in, I was then going to change AGP like
http://git.kernel.org/?p=linux/kernel/git/airlied/agp-2.6.git;a=shortlog;h=agp-pageattr2
I really should fix those patches up at some point, feel free to base
a system on those if someone objects to the method with the call site
doing the flush.
Dave.
next prev parent reply other threads:[~2008-08-04 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 6:51 Shaohua Li
2008-08-04 6:53 ` Dave Airlie [this message]
2008-08-04 7:14 ` Shaohua Li
2008-08-04 13:42 ` Arjan van de Ven
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=21d7e9970808032353m40fcea6dtbf1b7bc1c5cf06d9@mail.gmail.com \
--to=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=shaohua.li@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®