All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH Version 2 0/2] Adding to tracepoints
Date: Fri, 18 Dec 2015 14:50:09 -0500	[thread overview]
Message-ID: <CAHQdGtQiqUvYaQQ5Zc2z8qDv-XeAtVeZPL5HDM7KAd8jQjxWHA@mail.gmail.com> (raw)
In-Reply-To: <CAN-5tyHRPZ9Yd6iY7UTD5mEgCJH0T8usLgZfwXr+3JxdpidVMA@mail.gmail.com>

On Fri, Dec 18, 2015 at 1:52 PM, Olga Kornievskaia <aglo@umich.edu> wrote:
> Trond,
>
> I have had wireshark accept the patch to display the crc32 hash of the
> stateid's other field to match the output in the tracepoints. Can you
> please provide feedback about the proposed additions to tracepoints?
>

The patches looked OK to me. They do change message formats, but since
you are just appending to existing tracepoints, then that is ok.

I'm queuing these for the Linux 4.5 merge window.

> Thank you.
>
> On Wed, Dec 9, 2015 at 3:59 PM, Olga Kornievskaia <aglo@umich.edu> wrote:
>> Trond,
>>
>> Any thoughts on the patches?
>>
>> Thank you.
>>
>> On Tue, Nov 24, 2015 at 1:29 PM, Olga Kornievskaia <kolga@netapp.com> wrote:
>>> First patch adds stateid information to tracepoints (openstateid, delegation
>>> stateid, and locking stateid). Version 2 of this patch fixes two things from
>>> the previous version: (1) typo in printout missing ":" in one stateid, (2)
>>> close tracepoint should take stateid from the args instead of the state passed
>>> in as state's stateid could be delegation stateid.
>>>
>>> Second patch adds a new tracepoint nfs_cached_open()
>>>
>>> Olga Kornievskaia (2):
>>>   Adding stateid information to tracepoints
>>>   Adding tracepoint to cached open
>>>
>>>  fs/nfs/internal.h  |   9 ++
>>>  fs/nfs/nfs4proc.c  |  15 +--
>>>  fs/nfs/nfs4trace.h | 294 ++++++++++++++++++++++++++++++++++++++++++++++++-----
>>>  3 files changed, 286 insertions(+), 32 deletions(-)
>>>
>>> --
>>> 1.8.3.1
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2015-12-18 19:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 18:29 [PATCH Version 2 0/2] Adding to tracepoints Olga Kornievskaia
2015-11-24 18:29 ` [PATCH Version 2 1/2] Adding stateid information " Olga Kornievskaia
2015-11-24 18:29 ` [PATCH Version 2 2/2] Adding tracepoint to cached open Olga Kornievskaia
2015-12-09 20:59 ` [PATCH Version 2 0/2] Adding to tracepoints Olga Kornievskaia
2015-12-18 18:52   ` Olga Kornievskaia
2015-12-18 19:50     ` Trond Myklebust [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=CAHQdGtQiqUvYaQQ5Zc2z8qDv-XeAtVeZPL5HDM7KAd8jQjxWHA@mail.gmail.com \
    --to=trond.myklebust@primarydata.com \
    --cc=aglo@umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    /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.