All of lore.kernel.org
 help / color / mirror / Atom feed
From: Huang, Ying <ying.huang@linux.intel.com>
To: lkp@lists.01.org
Subject: Re: [SUNRPC] e1e5693191: +71.4% fsmark.files_per_sec
Date: Fri, 15 Jan 2016 09:35:03 +0800	[thread overview]
Message-ID: <8737tziq0o.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <CANn89i+7wN17Sz2JS_Z9ArC0C0TXpPa8mLM7X1j0=W3HwJhvjg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 566 bytes --]

Eric Dumazet <edumazet@google.com> writes:

> On Wed, Jan 13, 2016 at 7:05 PM, kernel test robot
> <ying.huang@linux.intel.com> wrote:
>> FYI, we noticed the below changes on
>>
>> git://internal_merge_and_test_tree
>> revert-e1e56931915cc3fafb4e17d4e1073e24c0a304ce-e1e56931915cc3fafb4e17d4e1073e24c0a304ce
>> commit e1e56931915cc3fafb4e17d4e1073e24c0a304ce ("SUNRPC: Fixup socket wait for memory")
>>
>
> Sure, this fixes the regression noticed in your other mail
> (ceb5d58b21: -69.2% fsmark.files_per_sec_)

Great!

Best Regards,
Huang, Ying


WARNING: multiple messages have this Message-ID (diff)
From: "Huang\, Ying" <ying.huang@linux.intel.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
	lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
	0day robot <fengguang.wu@intel.com>
Subject: Re: [lkp] [SUNRPC] e1e5693191: +71.4% fsmark.files_per_sec
Date: Fri, 15 Jan 2016 09:35:03 +0800	[thread overview]
Message-ID: <8737tziq0o.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <CANn89i+7wN17Sz2JS_Z9ArC0C0TXpPa8mLM7X1j0=W3HwJhvjg@mail.gmail.com> (Eric Dumazet's message of "Wed, 13 Jan 2016 19:11:56 -0800")

Eric Dumazet <edumazet@google.com> writes:

> On Wed, Jan 13, 2016 at 7:05 PM, kernel test robot
> <ying.huang@linux.intel.com> wrote:
>> FYI, we noticed the below changes on
>>
>> git://internal_merge_and_test_tree
>> revert-e1e56931915cc3fafb4e17d4e1073e24c0a304ce-e1e56931915cc3fafb4e17d4e1073e24c0a304ce
>> commit e1e56931915cc3fafb4e17d4e1073e24c0a304ce ("SUNRPC: Fixup socket wait for memory")
>>
>
> Sure, this fixes the regression noticed in your other mail
> (ceb5d58b21: -69.2% fsmark.files_per_sec_)

Great!

Best Regards,
Huang, Ying

  reply	other threads:[~2016-01-15  1:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14  3:05 [SUNRPC] e1e5693191: +71.4% fsmark.files_per_sec kernel test robot
2016-01-14  3:05 ` [lkp] " kernel test robot
2016-01-14  3:11 ` Eric Dumazet
2016-01-14  3:11   ` [lkp] " Eric Dumazet
2016-01-15  1:35   ` Huang, Ying [this message]
2016-01-15  1:35     ` Huang, Ying

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=8737tziq0o.fsf@yhuang-dev.intel.com \
    --to=ying.huang@linux.intel.com \
    --cc=lkp@lists.01.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.