mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: [GIT PULL] dma-mapping updates for Linux 6.8
Date: Mon, 8 Jan 2024 16:57:52 +0100	[thread overview]
Message-ID: <ZZwbgB9MRsqR5uE4@infradead.org> (raw)

The following changes since commit 3f7168591ebf7bbdb91797d02b1afaf00a4289b1:

  Merge tag '6.7-rc5-smb3-client-fixes' of git://git.samba.org/sfrench/cifs-2.6 (2023-12-14 19:57:42 -0800)

are available in the Git repository at:

  git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-6.8-2024-01-08

for you to fetch changes up to b07bc2347672cc8c7293c64499f1488278c5ca3d:

  dma-mapping: clear dev->dma_mem to NULL after freeing it (2023-12-15 12:32:45 +0100)

----------------------------------------------------------------
dma-mapping updates for Linux 6.8

 - reduce area lock contention for non-primary IO TLB pools (Petr Tesarik)
 - don't store redundant offsets in the dma_ranges stuctures
   (Robin Murphy)
 - clear dev->dma_mem when freeing per-device pools (Joakim Zhang)

----------------------------------------------------------------
Joakim Zhang (1):
      dma-mapping: clear dev->dma_mem to NULL after freeing it

Petr Tesarik (1):
      swiotlb: reduce area lock contention for non-primary IO TLB pools

Robin Murphy (1):
      dma-mapping: don't store redundant offsets

 drivers/acpi/scan.c        |  1 -
 drivers/of/address.c       |  1 -
 include/linux/dma-direct.h | 19 ++++++----
 kernel/dma/coherent.c      |  4 ++-
 kernel/dma/direct.c        |  1 -
 kernel/dma/swiotlb.c       | 90 ++++++++++++++++++++++++++++------------------
 6 files changed, 70 insertions(+), 46 deletions(-)

             reply	other threads:[~2024-01-08 15:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 15:57 Christoph Hellwig [this message]
2024-01-11 22:58 ` pr-tracker-bot

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=ZZwbgB9MRsqR5uE4@infradead.org \
    --to=hch@infradead.org \
    --cc=iommu@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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®