From: Christoph Lameter <cl@gentwo.org>
To: Wonhyuk Yang <vvghjk1234@gmail.com>
Cc: linux-mm@kvack.org, Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [Question] The necessity of transaction ID in SLUB.
Date: Tue, 23 Nov 2021 14:54:53 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2111231453330.18248@gentwo.de> (raw)
In-Reply-To: <CAEcHRTrTc-DzeyU4fetfyU3pQCS6A0pPexGe5c5yB94Z88ueHg@mail.gmail.com>
On Tue, 23 Nov 2021, Wonhyuk Yang wrote:
> Yes, that's why transaction id is made up of two part CPU id and event id
> (To guarantee there are no other events and migrations).
> And the guarantee is ultimately to protect cpu_slab->freelist.
Well that is the way it was initially because I thought along the same
way. You can simply revert the patches that introduced the TID to get that
version back (and the races too.....) if you want to try.
next prev parent reply other threads:[~2021-11-23 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 14:11 Wonhyuk Yang
2021-11-22 9:25 ` Christoph Lameter
2021-11-23 3:32 ` Wonhyuk Yang
2021-11-23 9:38 ` Christoph Lameter
2021-11-23 12:18 ` Wonhyuk Yang
2021-11-23 12:30 ` Wonhyuk Yang
2021-11-23 13:54 ` Christoph Lameter [this message]
2021-11-23 23:59 ` Wonhyuk 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=alpine.DEB.2.22.394.2111231453330.18248@gentwo.de \
--to=cl@gentwo.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=vvghjk1234@gmail.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