From: Christoph Hellwig <hch@infradead.org>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: mingo@kernel.org, peterz@infradead.org,
akpm@linux-foundation.org, torvalds@linux-foundation.org,
jack@suse.cz, kirill.shutemov@linux.intel.com,
ldufour@linux.vnet.ibm.com, mhocko@suse.com,
mgorman@techsingularity.net, linux-kernel@vger.kernel.org,
Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH 1/9] rbtree: Cache leftmost node internally
Date: Sat, 15 Jul 2017 03:54:33 -0700 [thread overview]
Message-ID: <20170715105433.GA31814@infradead.org> (raw)
In-Reply-To: <20170629171553.2146-2-dave@stgolabs.net>
Is the leftmost node so much more special than the rightmost one?
Just asking because I have some code that caches both of them, but
using your helpers would make it look very asymmetric..
next prev parent reply other threads:[~2017-07-15 10:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 17:15 [PATCH -next v3 0/9] rbtree: Cache leftmost node internally Davidlohr Bueso
2017-06-29 17:15 ` [PATCH 1/9] " Davidlohr Bueso
2017-07-15 10:54 ` Christoph Hellwig [this message]
2017-07-15 15:28 ` Davidlohr Bueso
2017-06-29 17:15 ` [PATCH 2/9] sched/fair: Replace cfs_rq->rb_leftmost Davidlohr Bueso
2017-06-29 17:15 ` [PATCH 3/9] sched/deadline: Replace earliest dl and rq leftmost caching Davidlohr Bueso
2017-06-29 17:15 ` [PATCH 4/9] locking/rtmutex: Replace top-waiter and pi_waiters " Davidlohr Bueso
2017-06-29 17:15 ` [PATCH 5/9] block/cfq: Replace cfq_rb_root " Davidlohr Bueso
2017-06-29 17:15 ` [PATCH 6/9] lib/interval_tree: Fast overlap detection Davidlohr Bueso
2017-06-29 17:15 ` [PATCH 7/9] lib/interval-tree: Correct comment wrt generic flavor Davidlohr Bueso
2017-06-29 17:15 ` [PATCH 8/9] procfs: Use faster rb_first_cached() Davidlohr Bueso
2017-06-29 17:15 ` [PATCH 9/9] fs/epoll: " Davidlohr Bueso
2017-07-05 17:47 ` [PATCH -next v3 0/9] rbtree: Cache leftmost node internally Peter Zijlstra
2017-07-19 22:54 ` Andrew Morton
2017-07-19 23:00 ` Davidlohr Bueso
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=20170715105433.GA31814@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dave@stgolabs.net \
--cc=dbueso@suse.de \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox