mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: fujita.tomonori@lab.ntt.co.jp
Cc: linux-kernel@vger.kernel.org, linux-sparc@vger.kernel.org,
	tomof@acm.org, akpm@linux-foundation.org
Subject: Re: [PATCH -mm 1/2] SPARC64: add the segment boundary checking to IOMMUs while merging SG entries
Date: Sat, 22 Mar 2008 17:23:05 -0700 (PDT)	[thread overview]
Message-ID: <20080322.172305.103826809.davem@davemloft.net> (raw)
In-Reply-To: <1205380027-28230-1-git-send-email-fujita.tomonori@lab.ntt.co.jp>

From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Date: Thu, 13 Mar 2008 12:47:06 +0900

> Some IOMMUs allocate memory areas spanning LLD's segment boundary
> limit. It forces low level drivers to have a workaround to adjust
> scatter lists that the IOMMU builds. We are in the process of making
> all the IOMMUs respect the segment boundary limits to remove such work
> around in LLDs.
> 
> SPARC64 IOMMUs were rewritten to use the IOMMU helper functions and
> the commit 89c94f2f70d093f59b55d3ea8042d13889169346 made the IOMMUs
> not allocate memory areas spanning the segment boundary limit.
> 
> However, SPARC64 IOMMUs allocate memory areas first then try to merge
> them (while some IOMMUs walk through all the sg entries to see how
> they can be merged first and allocate memory areas). So SPARC64 IOMMUs
> also need the boundary limit checking when they try to merge sg
> entries.
> 
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>

Acked-by: David S. Miller <davem@davemloft.net>

      parent reply	other threads:[~2008-03-23  0:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13  3:47 FUJITA Tomonori
2008-03-13  3:47 ` [PATCH -mm 2/2] SPARC64: remove unused calc_npages() in iommu_common.h FUJITA Tomonori
2008-03-23  0:23   ` David Miller
2008-03-23  0:23 ` David Miller [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=20080322.172305.103826809.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sparc@vger.kernel.org \
    --cc=tomof@acm.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
all inboxes | Powered by JetHome®