From: Ingo Molnar <mingo@kernel.org>
To: alexander.levin@verizon.com
Cc: "mingo@redhat.com" <mingo@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ben@decadent.org.uk" <ben@decadent.org.uk>,
Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [GIT PULL] liblockdep for 4.12
Date: Mon, 8 May 2017 08:18:45 +0200 [thread overview]
Message-ID: <20170508061845.rhoq73yentafplwv@gmail.com> (raw)
In-Reply-To: <20170507230444.hpglxzcdtiusxng7@sasha-lappy>
* alexander.levin@verizon.com <alexander.levin@verizon.com> wrote:
> On Fri, May 05, 2017 at 08:11:38AM +0200, Ingo Molnar wrote:
> > * alexander.levin@verizon.com <alexander.levin@verizon.com> wrote:
> > Could you please include all the patches as part of the pull request, so that
> > individual patches can be discussed?
>
> Sure, I'll resend.
>
> > In particular I'm wondering about:
> >
> > > tools/include/linux/jhash.h | 125 +++++++++++++++++++++++
> >
> > include/linux/jhash.h is 175 lines long - why not make an exact copy and keep it
> > synchronized the way perf does it?
>
> Including jhash() vs only jhash2() required pulling additional headers in.
> Since we don't need jhash() I preferred to drop it.
>
> Let me know if you'd prefer to do it the other way and include everything.
How many headers would that be? We already have tools/include/../bitops.h, so we'd
only need include/linux/unaligned/packed_struct.h, which looks straightforward and
smallish.
( That header includes kernel.h, but we have that in tools as well, so in theory
it could work. )
The principle would be to 'COW-share' as much code as possible, at least for
obvious arithmetics helpers - which hashes do appear to be.
Thanks,
Ingo
next prev parent reply other threads:[~2017-05-08 6:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 2:52 alexander.levin
2017-05-05 6:11 ` Ingo Molnar
2017-05-07 23:04 ` alexander.levin
2017-05-08 6:18 ` Ingo Molnar [this message]
2017-05-12 19:32 ` alexander.levin
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=20170508061845.rhoq73yentafplwv@gmail.com \
--to=mingo@kernel.org \
--cc=acme@infradead.org \
--cc=alexander.levin@verizon.com \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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®