From: "Тхай Кирилл" <tkhai@yandex.ru>
To: sparclinux@vger.kernel.org
Subject: Re: Re: [PATCH]sparc32: Fix impossibility of swap disabling after intensive swap using
Date: Fri, 30 Apr 2010 05:57:19 +0000 [thread overview]
Message-ID: <80141272607039@web66.yandex.ru> (raw)
In-Reply-To: <20100429.165815.235700454.davem@davemloft.net>
29.04.10, 16:58, "David Miller" <davem@davemloft.net>:
> From: Тхай Кирилл
> Date: Fri, 30 Apr 2010 03:28:35 +0400
>
> > The problem is that some "big" swap entries corresponds to "none" ptes and
> > they can't be unused in the function zap_pte_range when program is ending.
> > The function free_swap_and_cache isn't calls for that swap entries. And
> > swapoff syscall spin in infinity loop.
> > I hope my patch can be useful. Kernel version 2.6.33.3.
>
> I think we'll need to rearrange the bit usage to fix this instead of turning
> this off entirely.
Thank you for your reply.
I can mistake, but it seems to me, that pte_none is more wide check, than belonging pte to mmu device. In other case none_mask must be something like 0xF0000004, because hardware ignores ptes with zeroed lower two bits.
Execuse me if I expend your time.
Kirill
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-30 5:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 23:58 [PATCH]sparc32: Fix impossibility of swap disabling after David Miller
2010-04-30 5:57 ` Тхай Кирилл [this message]
2010-04-30 6:04 ` Re: Re: [PATCH]sparc32: Fix impossibility of swap disabling after intensive swap using Tkhai Kirill
2010-05-26 6:38 ` [PATCH]sparc32: Fix impossibility of swap disabling after David Miller
2010-05-27 20:28 ` Re: [PATCH]sparc32: Fix impossibility of swap disabling after intensive swap using Tkhai Kirill
2010-05-27 20:41 ` [PATCH]sparc32: Fix impossibility of swap disabling after David Miller
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=80141272607039@web66.yandex.ru \
--to=tkhai@yandex.ru \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.