From: Alex Elder <elder@ieee.org>
To: Douglas Fuller <dfuller@redhat.com>, Ilya Dryomov <idryomov@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH 0/3] rbd: header read/refresh improvements
Date: Fri, 24 Apr 2015 10:03:56 -0500 [thread overview]
Message-ID: <553A5B5C.9070909@ieee.org> (raw)
In-Reply-To: <9D2825F1-BA75-433E-9B92-63D405339F0E@redhat.com>
On 04/24/2015 09:40 AM, Douglas Fuller wrote:
>
>> On Apr 24, 2015, at 10:17 AM, Ilya Dryomov <idryomov@gmail.com>
>> wrote:
>>
>> On Fri, Apr 24, 2015 at 4:11 PM, Alex Elder <elder@ieee.org>
>> wrote:
>>> On 04/23/2015 02:06 PM, Douglas Fuller wrote:
>>>>
>>>> Support multiple class op calls in one ceph_msg and consolidate
>>>> rbd header read and refresh processes to use this feature to
>>>> reduce the number of ceph_msgs sent for that process. Refresh
>>>> features on header refresh and begin returning EIO if features
>>>> have changed since mapping.
>>>>
>>>> Douglas Fuller (3): ceph: support multiple class method calls
>>>> in one ceph_msg rbd: combine object method calls in header
>>>> refresh using fewer ceph_msgs rbd: re-read features during
>>>> header refresh and detect changes.
>>>>
>>>> drivers/block/rbd.c | 518
>>>> +++++++++++++++++++++++++++++-----------
>>>> include/linux/ceph/osd_client.h | 3 +- net/ceph/messenger.c
>>>> | 4 + net/ceph/osd_client.c | 92 ++++++- 4 files
>>>> changed, 470 insertions(+), 147 deletions(-)
>>>>
>>>
>>> In case Ilya or others don't get to it soon, I plan to review
>>> this series tomorrow.
>>
>> I was planning take a look while I'm the road during the weekend.
>>
>> Doug, from a quick look this revision still has a bunch of style
>> issues, most notably the alignment of function parameters and
>> braces around if / else. See Documentation/CodingStyle in the
>> kernel tree for examples.
>
> I needed to put out v2 in part because I squashed a couple fixup
> commits in the wrong place, leaving some things behind in #2 that
> were corrected in #3.
>
> I changed the braces in that version, but the function parameter
> indents are inconsistent throughout the code. I’ll try to come up
> with a compromise.
When in doubt, lean toward the style used in the rest of
the kernel. I used a few conventions that are not consistent
with that in a lot of places, and those can be gradually
phased toward what's recommended for the kernel. Some
examples are:
sizeof x or sizeof (x) --> sizeof(x)
(cast) foo --> (cast)foo
White space under comment blocks
static int\nfunction(...) -> static int function(...)
-Alex
>>
>> You might also want to run your patches through
>> scripts/checkpatch.pl, but take it with a grain of salt - it can be
>> a bit too extreme at times. No need to post v3 with just style
>> fixes, wait for more feedback.
>
> Thanks again for all feedback.
>
>>
>> Thanks,
>>
>> Ilya
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-04-24 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 19:06 [PATCH 0/3] rbd: header read/refresh improvements Douglas Fuller
2015-04-23 19:06 ` [PATCH 1/3] ceph: support multiple class method calls in one ceph_msg Douglas Fuller
2015-04-23 19:06 ` [PATCH 2/3] rbd: combine object method calls in header refresh using fewer ceph_msgs Douglas Fuller
2015-04-24 10:14 ` Mike Christie
2015-04-23 19:06 ` [PATCH 3/3] rbd: re-read features during header refresh and detect changes Douglas Fuller
2015-04-24 13:11 ` [PATCH 0/3] rbd: header read/refresh improvements Alex Elder
2015-04-24 13:25 ` Douglas Fuller
2015-04-24 14:17 ` Ilya Dryomov
2015-04-24 14:40 ` Douglas Fuller
2015-04-24 15:03 ` Alex Elder [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=553A5B5C.9070909@ieee.org \
--to=elder@ieee.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dfuller@redhat.com \
--cc=idryomov@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.