public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] PATCH: performance problems with swiotlb.c
Date: Mon, 03 Dec 2001 21:55:36 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805590@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805583@msgid-missing>

>>>>> On Mon, 3 Dec 2001 12:12:07 -0800, "Luck, Tony" <tony.luck@intel.com> said:

  Tony> The basis of the fix is to partition the space reserved for
  Tony> bounce buffers into smaller segments so that we place an upper
  Tony> bound on the amount of work needed to coalesce blocks.

Looks good to me.  I applied the patch,

  Tony> In addition to the performace boost, this patch also fixes one
  Tony> real bug that Dori found while testing.  map_single() would
  Tony> pick a "stride" based on the number of slots needed for the
  Tony> request ... but if this stride is not a power of two, the "do
  Tony> { ... } while (index != wrap);" loop can spin indefinitely. He
  Tony> changed that to use a stride of 1 because he couldn't see the
  Tony> benefit of the larger stride ... nor can I ... e.g.  when
  Tony> looking for 5 slots you might look at an allocation map that
  Tony> looks like this:

  Tony> 	3 <- look here, 3<5 so skip down 5 slots 2 1 0 5 4 <-
  Tony> now look here, missing the large enough block that began on
  Tony> the previous slot.

I'm not sure either.  I assume the stride was intended to reduce
searching overheads.  Perhaps Asit or Goutham would know?

Thanks,

	--david


      reply	other threads:[~2001-12-03 21:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 20:12 [Linux-ia64] PATCH: performance problems with swiotlb.c Luck, Tony
2001-12-03 21:55 ` David Mosberger [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=marc-linux-ia64-105590698805590@msgid-missing \
    --to=davidm@hpl.hp.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox