public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve French <smfrench@austin.rr.com>
To: tmolina@cox.net, linux-kernel@vger.kernel.org
Subject: compile problem with 2.5.61-bk
Date: Sun, 16 Feb 2003 14:21:34 -0600	[thread overview]
Message-ID: <3E4FF2CE.60208@austin.rr.com> (raw)

Those two functions are not exported (see e.g. ksyms.c) so are not 
available for modules to access but work when built as part of the kernel.
For the time being this means the CIFS VFS can not be built as a module.
Looks like I will have to figure out an alternate way to get at those two
functions either directly by exporting them or preferably by calling them 
indirectly - there may be a way to change fs/cifs/file.c to use the similar
function read_cache_pages directly as nfs does (which presumably is an 
exported function) but it wasn't obvious at the time since the cifs vfs 
preferably reads the equivalent of 4 pages at a time (rather than one 
4K page) across the network and the addition of support of readpages 
(with 16K reads in the readahead path) to the cifs vfs demonstrated a 
measurable performance benefit) even in the worst case (to loaded 
servers or on busy network segments the improvement would be more 
dramatic).

I will take a look at this later tonight to see if I can recode 
cifs_readpages to bypass the need for the additional exports.


Thomas Molina wrote: 
>After syncing with bk this morning I get the following errors during make 
>modules

>*** Warning: "add_to_page_cache" [fs/cifs/cifs.ko] undefined!
>*** Warning: "__pagevec_lru_add" [fs/cifs/cifs.ko] undefined!

>which I don't understand since those items are defined in files included 
>by fs/cifs/file.c




             reply	other threads:[~2003-02-16 20:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-16 20:21 Steve French [this message]
2003-02-16 22:23 ` compile problem with 2.5.61-bk Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2003-02-16 16:31 Thomas Molina

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=3E4FF2CE.60208@austin.rr.com \
    --to=smfrench@austin.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmolina@cox.net \
    /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