From: Davidlohr Bueso <dave@stgolabs.net>
To: Oleg Drokin <oleg.drokin@intel.com>
Cc: mingo@kernel.org, peterz@infradead.org,
akpm@linux-foundation.org, jack@suse.cz,
kirill.shutemov@linux.intel.com, mhocko@suse.com,
mgorman@techsingularity.net, linux-kernel@vger.kernel.org,
andreas.dilger@intel.com, jsimmons@infradead.org,
lustre-devel@lists.lustre.org, Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH 5/5] staging/lustre: Use generic range rwlock
Date: Wed, 8 Mar 2017 07:02:27 -0800 [thread overview]
Message-ID: <20170308150227.GA20801@linux-80c1.suse> (raw)
In-Reply-To: <512F521B-5FA2-4ED8-82F4-5CD90A381813@intel.com>
On Tue, 07 Mar 2017, Oleg Drokin wrote:
>On Mar 7, 2017, at 12:03 AM, Davidlohr Bueso wrote:
>
>> This replaces the in-house version, which is also derived
>> from Jan's interval tree implementation.
>>
>> Cc: oleg.drokin@intel.com
>> Cc: andreas.dilger@intel.com
>> Cc: jsimmons@infradead.org
>> Cc: lustre-devel@lists.lustre.org
>>
>> Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
>> ---
>> XXX: compile tested only. In house uses 'ulong long', generic uses 'ulong', is this a problem?
>
>Hm, cannot seem to find the other patches in this series anywhere to verify and my subscription to linux-kernel broke as it turns out.
You can find the full series here:
https://lwn.net/Articles/716383/
>You mean the range is ulong? So only can have this working up to 2G offsets on the
>32bit systems and then wrap around?
Yes.
Thanks,
Davidlohr
next prev parent reply other threads:[~2017-03-08 15:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 5:03 [PATCH 0/5] locking Introduce range reader/writer lock Davidlohr Bueso
2017-03-07 5:03 ` [PATCH 1/5] locking: " Davidlohr Bueso
2017-03-09 11:03 ` Jan Kara
2017-03-28 10:00 ` Laurent Dufour
2017-03-28 16:39 ` Davidlohr Bueso
2017-03-28 16:58 ` Kirill A. Shutemov
2017-03-29 8:38 ` Laurent Dufour
2017-03-29 15:31 ` Davidlohr Bueso
2017-03-29 15:40 ` Kirill A. Shutemov
2017-03-29 16:10 ` Davidlohr Bueso
2017-04-03 14:19 ` Laurent Dufour
2017-04-03 15:26 ` Davidlohr Bueso
2017-04-03 16:06 ` Jan Kara
2017-04-04 15:31 ` Davidlohr Bueso
2017-03-29 8:56 ` Peter Zijlstra
2017-03-29 15:12 ` Davidlohr Bueso
2017-03-29 8:59 ` Peter Zijlstra
2017-03-29 9:08 ` Peter Zijlstra
2017-03-29 15:05 ` Davidlohr Bueso
2017-03-29 9:11 ` Peter Zijlstra
2017-03-29 9:44 ` Peter Zijlstra
2017-03-29 10:35 ` Peter Zijlstra
2017-03-29 10:49 ` Peter Zijlstra
2017-03-29 15:14 ` Davidlohr Bueso
2017-03-30 14:56 ` Laurent Dufour
2017-03-30 17:13 ` Davidlohr Bueso
2017-03-07 5:03 ` [PATCH 2/5] locking/locktorture: Fix rwsem reader_delay Davidlohr Bueso
2017-03-07 5:03 ` [PATCH 3/5] locking/locktorture: Fix num reader/writer corner cases Davidlohr Bueso
2017-03-07 5:03 ` [PATCH 4/5] locking/locktorture: Support range rwlocks Davidlohr Bueso
2017-03-07 5:03 ` [PATCH 5/5] staging/lustre: Use generic range rwlock Davidlohr Bueso
2017-03-07 6:05 ` Oleg Drokin
2017-03-08 15:02 ` Davidlohr Bueso [this message]
2017-03-09 8:56 ` kbuild test robot
2017-03-09 14:40 ` kbuild test robot
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=20170308150227.GA20801@linux-80c1.suse \
--to=dave@stgolabs.net \
--cc=akpm@linux-foundation.org \
--cc=andreas.dilger@intel.com \
--cc=dbueso@suse.de \
--cc=jack@suse.cz \
--cc=jsimmons@infradead.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=oleg.drokin@intel.com \
--cc=peterz@infradead.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