public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Suparna Bhattacharya <suparna@in.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lighten mmlist_lock
Date: Sun, 5 Sep 2004 17:33:48 -0700	[thread overview]
Message-ID: <20040906003348.GE3106@holomorphy.com> (raw)
In-Reply-To: <20040905234101.GD3106@holomorphy.com>

On Sun, Sep 05, 2004 at 04:41:01PM -0700, William Lee Irwin III wrote:
> The ticketing scheme -based alternative only really has to involve a
> pgd coming into active use, so s/mmlist addition points/pgd reuse points/
> would be better here to retain instructions for anyone suffering from
> contention on pgd_lock how to address the issue with the new mmlist
> scheme. pgd_alloc() and pgd_free() actually appear to suffice, and it's
> also worth mentioning the ticketing scheme's MMU context switch and
> smp_call_function() requirements as well.
> So I'll send an update to that comment a bit later on.

Actually we should probably #ifdef the whole change_page_attr() mess
on CONFIG_AGP; any box that cares about the overhead will be headless
and thus able to remove the state maintenance on behalf of AGP. AGP's
introduction of physical aliases (i.e. 2 physical addresses aliasing
the same memory) without cache coherency protocol support was beyond
insane and people should be able to opt out of the overhead when they
don't want or need AGP support.


-- wli

      reply	other threads:[~2004-09-06  0:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05 22:47 [PATCH] lighten mmlist_lock Hugh Dickins
2004-09-05 23:41 ` William Lee Irwin III
2004-09-06  0:33   ` William Lee Irwin III [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=20040906003348.GE3106@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suparna@in.ibm.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