From: Hugh Dickins <hugh@veritas.com>
To: Suparna Bhattacharya <suparna@in.ibm.com>
Cc: linux-mm@kvack.org
Subject: Re: use_mm/unuse_mm correctness
Date: Mon, 16 Jun 2003 10:30:43 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0306161029030.1469-100000@localhost.localdomain> (raw)
In-Reply-To: <20030616121322.A10735@in.ibm.com>
On Mon, 16 Jun 2003, Suparna Bhattacharya wrote:
>
> However, in the aio case, use_mm and unuse_mm are called
> only by workqueue threads, so there shouldn't be any
> migration even if a pre-empt occurs (cpus_allowed is fixed
> to a particular cpu), should it ?
Ah, yes, I certainly hope the cpu can't change in such a case!
Sorry for the noise, I hope someone else can help,
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-06-16 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 3:59 Suparna Bhattacharya
2003-06-16 6:16 ` Hugh Dickins
2003-06-16 6:43 ` Suparna Bhattacharya
2003-06-16 9:30 ` Hugh Dickins [this message]
2003-06-17 0:06 Venu Vadapalli
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=Pine.LNX.4.44.0306161029030.1469-100000@localhost.localdomain \
--to=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=suparna@in.ibm.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