From: Wei Yang <richard.weiyang@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Wei Yang <richardw.yang@linux.intel.com>,
"Huang, Ying" <ying.huang@intel.com>,
kernel test robot <rong.a.chen@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [driver core] 570d020012: will-it-scale.per_thread_ops -12.2% regression
Date: Thu, 21 Feb 2019 21:40:30 +0000 [thread overview]
Message-ID: <20190221214030.niwvh3xjlioi3myd@master> (raw)
In-Reply-To: <20190221091217.GA18701@kroah.com>
On Thu, Feb 21, 2019 at 10:12:17AM +0100, Greg Kroah-Hartman wrote:
>On Thu, Feb 21, 2019 at 04:39:27PM +0800, Wei Yang wrote:
>> >>> I don't think this is an issues of struct device. As you said, struct
>> >>> device isn't access much during test. Struct device may share slab page
>> >>> with some other data structures (signal related, or fd related (as in
>> >>> some other test cases)), so that the alignment of these data structures
>> >>> are affected, so caused the performance regression.
>> >>
>> >> But allocation of a structure should always be "properly" aligned, no
>> >> matter what something else did in the system as that is what kmalloc
>> >> ensures. If not, then we have problems in our memory allocator :)
>> >>
>> >> So something is odd here, but I don't think that is it...
>> >
>> >If all these data structure are allocated with kmalloc() instead of
>> >kmem_cache_alloc(), then my guessing above seems incorrect ...
>> >
>>
>> Seems we don't have special kmem_cache for device and device_private.
>
>Nor do we need one :)
>
>Remember, 'struct device' is included inside lots of other structures
>already, it is not very often created "on its own."
>
You are right, I get your point.
>thanks,
>
>greg k-h
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2019-02-21 21:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 7:54 kernel test robot
[not found] ` <20190219005945.GA16734@richard>
2019-02-19 12:19 ` Greg Kroah-Hartman
2019-02-21 3:10 ` kernel test robot
2019-02-21 3:46 ` Wei Yang
2019-02-21 4:46 ` Huang, Ying
2019-02-21 6:02 ` Wei Yang
2019-02-21 6:29 ` Huang, Ying
2019-02-21 5:46 ` kernel test robot
2019-02-21 7:10 ` Greg Kroah-Hartman
2019-02-21 7:18 ` Huang, Ying
2019-02-21 7:35 ` Greg Kroah-Hartman
2019-02-21 8:30 ` Huang, Ying
[not found] ` <20190221083926.GA7834@richard>
2019-02-21 9:12 ` Greg Kroah-Hartman
2019-02-21 21:40 ` Wei Yang [this message]
2019-02-21 7:53 ` Wei Yang
2019-02-21 22:31 ` Wei Yang
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=20190221214030.niwvh3xjlioi3myd@master \
--to=richard.weiyang@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=rafael.j.wysocki@intel.com \
--cc=richardw.yang@linux.intel.com \
--cc=rong.a.chen@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=ying.huang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®