| Date | Fri, 27 Mar 2015 17:06:13 -0400 | From | Vivek Goyal <> | Subject | Re: [PATCH 21/48] writeback: make backing_dev_info host cgroup-specific bdi_writebacks |
| |
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
|