..snip.. > > > > > > Anyway, I made v2 patches by using swiotlb related definitions. Would you check it? > > > > Did I miss that email? As in was I cc-ed? > > This was my fault. When I submitted v2 patches, I didn't include your email and iommu mailing list... No problem. > > > > https://patchwork.kernel.org/patch/10018879/ > > > > Why not use IO_TLB_SEGSIZE << IO_TLB_SHIFT or alternatively > > swiotlb_max_segment? See 5584f1b1d73e9 > > I already made such a patch as v2 and it was merged into mmc.git / fixes branch. > > https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git/commit/?h=fixes&id=e90e8da72ad694a16a4ffa6e5adae3610208f73b What happens if the user has swiotlb=4096 on the command line (meaning less than the default value)? Your max value will be incorrect. Could you use swiotlb_max_segment? -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
