Linux-NVME Archive on
 help / color / Atom feed
* IOMMU incompatibility with discard on certain devices
@ 2019-11-10 15:11 Philip Langdale
  0 siblings, 0 replies; only message in thread
From: Philip Langdale @ 2019-11-10 15:11 UTC (permalink / raw)
  To: linux-nvme

Hi all,

I'm writing to highlight a problem that is affecting users of certain
nvme ssds as discussed here:

The problem has been narrowed down to some devices always doing page
aligned reads when reading the list of segments to discard, rather than
reading the exact size passed. When an enforcing IOMMU is used (both
Intel and AMD systems exhibit the same behaviour in the reports), these
page-aligned reads are rejected because they are larger than the actual

In the bugzilla bug, a patch was proposed to add a device quirk that
ensures the segment list allocation is page-aligned, and this solved
the problem for everyone who tried it. Another patch was offered that
simply always page-aligns the allocations and perhaps that's
actually better?

If I was the patch author, I would have sent the quirk patch to the
list, but as I am not, I can't sign-off on it. It would be great if
someone could look at this, and we can get a fix committed.



Linux-nvme mailing list

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-10 15:11 IOMMU incompatibility with discard on certain devices Philip Langdale

Linux-NVME Archive on

Archives are clonable:
	git clone --mirror linux-nvme/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-nvme linux-nvme/ \
	public-inbox-index linux-nvme

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone