From: Wonhyuk Yang <vvghjk1234@gmail.com>
To: Christoph Lameter <cl@gentwo.org>
Cc: linux-mm@kvack.org, Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [Question] The necessity of transaction ID in SLUB.
Date: Wed, 24 Nov 2021 08:59:20 +0900 [thread overview]
Message-ID: <CAEcHRTo8wKgLLzjxgH+-fva87k7mhQFpzVQae9z5n+9orok38w@mail.gmail.com> (raw)
In-Reply-To: <CAEcHRTrTc-DzeyU4fetfyU3pQCS6A0pPexGe5c5yB94Z88ueHg@mail.gmail.com>
Now I know what I missed!
I missed that the freepointer may no more be valid because any other
preemptions. Also, It is possible that cpu_slab->freelist is unchanged
but it's freepointer may be changed. This is why we guarantee that
there is no update before, right?
Thanks to the answer, I was able to solve my question.
prev parent reply other threads:[~2021-11-24 0:08 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
2021-11-23 23:59 ` Wonhyuk Yang [this message]
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=CAEcHRTo8wKgLLzjxgH+-fva87k7mhQFpzVQae9z5n+9orok38w@mail.gmail.com \
--to=vvghjk1234@gmail.com \
--cc=cl@gentwo.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.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