Messages in this thread | | | Subject | Re: [patch 1/1] Writeback fix for concurrent large and small file writes | From | Frans Pop <> | Date | Thu, 29 Nov 2007 03:13:41 +0100 |
| |
Two typos in comments.
Cheers, FJP
Michael Rubin wrote: > + * The flush tree organizes the dirtied_when keys with the rb_tree. Any > + * inodes with a duplicate dirtied_when value are link listed together. > This + * link list is sorted by the inode's i_flushed_when. When both the > + * dirited_when and the i_flushed_when are indentical the order in the > + * linked list determines the order we flush the inodes.
s/dirited_when/dirtied_when/
> + * Here is where we interate to find the next inode to process. The > + * strategy is to first look for any other inodes with the same > dirtied_when + * value. If we have already processed that node then we > need to find + * the next highest dirtied_when value in the tree.
s/interate/iterate/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |