From: Evgeniy Polyakov <zbr@ioremap.net>
To: GregKH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
netdev@vger.kernel.org, Evgeniy Polyakov <zbr@ioremap.net>
Subject: [9/9] pohmelfs: kconfig/makefile and vfs changes.
Date: Mon, 9 Feb 2009 17:02:42 +0300 [thread overview]
Message-ID: <1234188162-14727-10-git-send-email-zbr@ioremap.net> (raw)
In-Reply-To: <1234188162-14727-9-git-send-email-zbr@ioremap.net>
This patch adds Kconfig and Makefile entries and exports to
VFS functions to be used by POHMELFS.
Signed-off-by: Evgeniy Polyakov <zbr@ioremap.net>
diff --git a/mm/filemap.c b/mm/filemap.c
index f3e5f89..3f77548 100644
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -513,6 +513,7 @@ int add_to_page_cache_lru(struct page *page, struct address_space *mapping,
}
return ret;
}
+EXPORT_SYMBOL_GPL(add_to_page_cache_lru);
#ifdef CONFIG_NUMA
struct page *__page_cache_alloc(gfp_t gfp)
@@ -627,6 +628,7 @@ int __lock_page_killable(struct page *page)
return __wait_on_bit_lock(page_waitqueue(page), &wait,
sync_page_killable, TASK_KILLABLE);
}
+EXPORT_SYMBOL_GPL(__lock_page_killable);
/**
* __lock_page_nosync - get a lock on the page, without calling sync_page()
diff --git a/drivers/staging/Kconfig b/drivers/staging/Kconfig
index 5d457c9..a089649 100644
--- a/drivers/staging/Kconfig
+++ b/drivers/staging/Kconfig
@@ -41,6 +41,8 @@ config STAGING_EXCLUDE_BUILD
if !STAGING_EXCLUDE_BUILD
+source "drivers/staging/pohmelfs/Kconfig"
+
source "drivers/staging/et131x/Kconfig"
source "drivers/staging/slicoss/Kconfig"
diff --git a/drivers/staging/Makefile b/drivers/staging/Makefile
index 71c4d53..631ce75 100644
--- a/drivers/staging/Makefile
+++ b/drivers/staging/Makefile
@@ -3,6 +3,7 @@
# fix for build system bug...
obj-$(CONFIG_STAGING) += staging.o
+obj-$(CONFIG_POHMELFS) += pohmelfs/
obj-$(CONFIG_ET131X) += et131x/
obj-$(CONFIG_SLICOSS) += slicoss/
obj-$(CONFIG_SXG) += sxg/
diff --git a/drivers/staging/pohmelfs/Makefile b/drivers/staging/pohmelfs/Makefile
new file mode 100644
index 0000000..196561c
--- /dev/null
+++ b/drivers/staging/pohmelfs/Makefile
@@ -0,0 +1,3 @@
+obj-$(CONFIG_POHMELFS) += pohmelfs.o
+
+pohmelfs-y := inode.o config.o dir.o net.o path_entry.o trans.o crypto.o lock.o mcache.o
diff --git a/drivers/staging/pohmelfs/Kconfig b/drivers/staging/pohmelfs/Kconfig
new file mode 100644
index 0000000..82d13ad
--- /dev/null
+++ b/drivers/staging/pohmelfs/Kconfig
@@ -0,0 +1,23 @@
+config POHMELFS
+ tristate "POHMELFS filesystem support"
+ select CONNECTOR
+ help
+ POHMELFS stands for Parallel Optimized Host Message Exchange Layered File System.
+ This is a network filesystem which supports coherent caching of data and metadata
+ on clients.
+
+config POHMELFS_DEBUG
+ bool "POHMELFS debugging"
+ depends on POHMELFS
+ default n
+ help
+ Turns on excessive POHMELFS debugging facilities.
+ You usually do not want to slow things down noticebly and get really lots of kernel
+ messages in syslog.
+
+config POHMELFS_CRYPTO
+ bool "POHMELFS crypto support"
+ depends on CONFIG_CRYPTO_BLKCIPHER && CONFIG_CRYPTO_HASH
+ help
+ This option allows to encrypt and/or protect with strong cryptographic hash all dataflow
+ between server and clients. Each config group can have own keys.
next prev parent reply other threads:[~2009-02-09 14:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 14:02 [0/9] pohmelfs for drivers/staging Evgeniy Polyakov
2009-02-09 14:02 ` [1/9] pohmelfs: documentation Evgeniy Polyakov
2009-02-09 14:02 ` [2/9] pohmelfs: configuration interface Evgeniy Polyakov
2009-02-09 14:02 ` [3/9] pohmelfs: crypto processing Evgeniy Polyakov
2009-02-09 14:02 ` [4/9] pohmelfs: directory operations Evgeniy Polyakov
2009-02-09 14:02 ` [5/9] pohmelfs: inode operations Evgeniy Polyakov
2009-02-09 14:02 ` [6/9] pohmelfs: distributed locking and cache coherency protocol Evgeniy Polyakov
2009-02-09 14:02 ` [7/9] pohmelfs: network operations Evgeniy Polyakov
2009-02-09 14:02 ` [8/9] pohmelfs: transaction layer Evgeniy Polyakov
2009-02-09 14:02 ` Evgeniy Polyakov [this message]
2009-02-09 21:30 ` [10/9] pohmelfs: select crypto modules from the config Evgeniy Polyakov
2009-02-12 19:41 ` [0/9] pohmelfs for drivers/staging Greg KH
2009-02-12 20:58 ` Evgeniy Polyakov
-- strict thread matches above, loose matches on Subject: below --
2008-12-26 14:18 [0/9] pohmelfs: The Great Southern Trendkill release Evgeniy Polyakov
2008-12-26 14:18 ` [1/9] pohmelfs: documentation Evgeniy Polyakov
2008-12-26 14:18 ` [2/9] pohmelfs: configuration interface Evgeniy Polyakov
2008-12-26 14:18 ` [3/9] pohmelfs: crypto processing Evgeniy Polyakov
2008-12-26 14:18 ` [4/9] pohmelfs: directory operations Evgeniy Polyakov
2008-12-26 14:18 ` [5/9] pohmelfs: inode operations Evgeniy Polyakov
2008-12-26 14:18 ` [6/9] pohmelfs: distributed locking and cache coherency protocol Evgeniy Polyakov
2008-12-26 14:18 ` [7/9] pohmelfs: network operations Evgeniy Polyakov
2008-12-26 14:18 ` [8/9] pohmelfs: transaction layer Evgeniy Polyakov
2008-12-26 14:18 ` [9/9] pohmelfs: kconfig/makefile and vfs changes Evgeniy Polyakov
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=1234188162-14727-10-git-send-email-zbr@ioremap.net \
--to=zbr@ioremap.net \
--cc=greg@kroah.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®