From: "Loke, Chetan" <Chetan.Loke@netscout.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>, netdev@vger.kernel.org
Cc: Konrad Wilk <konrad.wilk@oracle.com>, linux-mm <linux-mm@kvack.org>
Subject: RE: [RFC] non-preemptible kernel socket for RAMster
Date: Tue, 5 Jul 2011 12:36:43 -0400 [thread overview]
Message-ID: <D3F292ADF945FB49B35E96C94C2061B91257D65C@nsmail.netscout.com> (raw)
In-Reply-To: <4232c4b6-15be-42d8-be42-6e27f9188ce2@default>
> -----Original Message-----
> From: netdev-owner@vger.kernel.org [mailto:netdev-
> owner@vger.kernel.org] On Behalf Of Dan Magenheimer
> Sent: July 05, 2011 11:54 AM
> To: netdev@vger.kernel.org
> Cc: Konrad Wilk; linux-mm
> Subject: [RFC] non-preemptible kernel socket for RAMster
>
> In working on a kernel project called RAMster* (where RAM on a
> remote system may be used for clean page cache pages and for swap
> pages), I found I have need for a kernel socket to be used when
How is RAMster+swap different than NBD's (pending etc?)support for SWAP
over NBD?
Chetan Loke
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-07-05 16:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 15:54 Dan Magenheimer
2011-07-05 16:30 ` Eric Dumazet
2011-07-05 17:25 ` Dan Magenheimer
2011-07-05 18:23 ` Eric Dumazet
2011-07-05 19:07 ` Dan Magenheimer
2011-07-05 16:36 ` Loke, Chetan [this message]
2011-07-05 17:25 ` Dan Magenheimer
2011-07-05 17:52 ` Loke, Chetan
2011-07-05 19:18 ` Dan Magenheimer
2011-07-05 22:27 ` Loke, Chetan
2011-07-06 1:05 ` Dan Magenheimer
2011-07-06 18:12 ` Loke, Chetan
2011-07-07 15:34 ` Dan Magenheimer
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=D3F292ADF945FB49B35E96C94C2061B91257D65C@nsmail.netscout.com \
--to=chetan.loke@netscout.com \
--cc=dan.magenheimer@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-mm@kvack.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox