From: ebiederm+eric@npwt.net (Eric W. Biederman)
To: linux-mm@kvack.org
Subject: Q: Swap Locking Reinstatement
Date: 12 May 1998 20:57:05 -0500 [thread overview]
Message-ID: <m1somf2arx.fsf@flinx.npwt.net> (raw)
Recently the swap lockmap has been readded.
Was that just as a low cost sanity check, to use especially while
there were bugs in some of the low level disk drivers?
Was there something that really needs the swap lockmap?
The reason I am asking is that this causes conflicts with my shmfs
kernel patches. I directly read/write swap pages through a variation
of rw_swap_page, and during I/O they must stay in the page cache, but
_not_ on the swapper inode, and the way the swap lockmap is currently
implemented causes a problem.
Eric
next reply other threads:[~1998-05-13 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-13 1:57 Eric W. Biederman [this message]
1998-05-19 22:46 ` Stephen C. Tweedie
1998-05-27 15:15 ` Eric W. Biederman
1998-06-04 3:20 ` Eric W. Biederman
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=m1somf2arx.fsf@flinx.npwt.net \
--to=ebiederm+eric@npwt.net \
--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