From: Rajagopal Ananthanarayanan <ananth@sgi.com>
To: linux-mm@kvack.org
Subject: waiting on writepage operation
Date: Wed, 05 Jul 2000 18:05:56 -0700 [thread overview]
Message-ID: <3963DB74.808D8D90@sgi.com> (raw)
Noticed that filemap_write_page has a wait
parameter that is being unused. When called
from the swapout path, the calling routine
does not intend the operation to block ...
so it calls filemap_write_page with wait = 0.
However, the writepage operation of the
address space does not support the notion of
waiting. Is there a reason to hope that the
wait argument might become part of writepage()?
It will be great to work out a dead-lock situation
in XFS by simply bailing out of the writepage
if it was called with wait = 0.
Thanks for any suggestions,
--------------------------------------------------------------------------
Rajagopal Ananthanarayanan ("ananth")
Member Technical Staff, SGI.
--------------------------------------------------------------------------
--
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.eu.org/Linux-MM/
reply other threads:[~2000-07-06 0:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3963DB74.808D8D90@sgi.com \
--to=ananth@sgi.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