Date: Wed, 30 Mar 2016 14:00:13 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 208365] [umass] Cannot fsck 3TB USB disk Message-ID: <bug-208365-6-QzVXtVBwDW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-208365-6@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208365 --- Comment #16 from Roger Pau Monné <royger@freebsd.org> --- (In reply to Hans Petter Selasky from comment #15) Yes, there are several optimizations that can be applied in order to improve the patch. As I've noted in the comment, this is just an initial approach to make sure the problem is caused by not bouncing the whole region (and then the offsets don't match anymore). Regarding the "again" label, I'm not really sure we can get rid of it, for the mapped case (_bus_dmamap_count_pages) it looks like we can remove it, but for the other cases it depends on whether maxsegsz is a multiple of a PAGE_SIZE, or else we might end up with segments that don't have consecutive offsets AFAICT. -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-208365-6-QzVXtVBwDW>