Re: [PATCH 21/48] writeback: make backing_dev_info host cgroup-specific bdi_writebacks
From: Vivek Goyal <vgoyal@redhat.com>
Date: 2015-03-27 21:06:13
Also in:
linux-fsdevel, linux-mm, lkml
From: Vivek Goyal <vgoyal@redhat.com>
Date: 2015-03-27 21:06:13
Also in:
linux-fsdevel, linux-mm, lkml
On Mon, Mar 23, 2015 at 12:54:32AM -0400, Tejun Heo wrote: [..]
+/**
+ * inode_attach_wb - associate an inode with its wb
+ * @inode: inode of interest
+ * @page: page being dirtied (may be NULL)
+ *
+ * If @inode doesn't have its wb, associate it with the wb matching the
+ * memcg of @page or, if @page is NULL, %current. May be called w/ or w/o
+ * @inode->i_lock.
+ */
+static inline void inode_attach_wb(struct inode *inode, struct page *page)
+{
+ if (!inode->i_wb)
+ __inode_attach_wb(inode, page);
+}Hi Tejun, I was curious to know that why do we need this "struct page *page" when trying to attach a inode to a bdi_writeback. Is using current's cgroup always not sufficient? Thanks Vivek -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>