Re: [PATCH v3] iomap: avoid redundant fault_in_iov_iter_readable() judgement when use larger chunks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This looks generally good.  But a few nitpicks:

 - please split the mapping_max_folio_size addition into a separate
   well-documented helper instead of merging it into the iomap change.
 - judgment is a really weird term for code.  Here is a subject I came
   up with, which might not be perfect:

"iomap: fault in smaller chunks for non-large folio mappings"





[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux