From: "David Laight" <David.Laight@ACULAB.COM>
To: Rui Xiang <rui.xiang@huawei.com>, Greg KH <gregkh@linuxfoundation.org>
Cc: linux-s390@vger.kernel.org, linux-ia64@vger.kernel.org,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, viro@zeniv.linux.org.uk,
cgroups@vger.kernel.org, linux-fsdevel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net,
linuxppc-dev@lists.ozlabs.org
Subject: RE: [PATCH 0/2] fs: supply inode uid/gid setting interface
Date: Tue, 27 Aug 2013 10:20:50 +0100 [thread overview]
Message-ID: <AE90C24D6B3A694183C094C60CF0A2F6026B7307@saturn3.aculab.com> (raw)
In-Reply-To: <5217100E.6080506@huawei.com>
> Subject: Re: [PATCH 0/2] fs: supply inode uid/gid setting interface
>
> On 2013/8/23 12:10, Greg KH wrote:
> > On Fri, Aug 23, 2013 at 10:48:36AM +0800, Rui Xiang wrote:
> >> This patchset implements an accessor functions to set uid/gid
> >> in inode struct. Just finish code clean up.
> >
> > Why?
> >
> It can introduce a new function to reduce some codes.
> Just clean up.
In what sense is it a 'cleanup' ?
To my mind it just means that anyone reading the code has
to go and look at another file in order to see what the
function does (it might be expected to be more complex).
It also adds run time cost, while probably not directly
measurable I suspect it more than doubles the execution
time of that code fragment - do that everywhere and the
system will run like a sick pig.
The only real use for accessor functions is when you
don't want the structure offset to be public.
In this case that is obviously not the case since
all the drivers are directly accessing other members
of the structure.
David
--
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>
prev parent reply other threads:[~2013-08-27 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 2:48 Rui Xiang
2013-08-23 2:48 ` [PATCH 1/2] fs: implement inode uid/gid setting function Rui Xiang
2013-08-23 2:48 ` [PATCH 2/2] fs: use inode_set_user to set uid/gid of inode Rui Xiang
2013-08-23 5:21 ` David Miller
2013-08-23 4:10 ` [PATCH 0/2] fs: supply inode uid/gid setting interface Greg KH
2013-08-23 7:32 ` Rui Xiang
2013-08-27 9:20 ` David Laight [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AE90C24D6B3A694183C094C60CF0A2F6026B7307@saturn3.aculab.com \
--to=david.laight@aculab.com \
--cc=cgroups@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=rui.xiang@huawei.com \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox