LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Siva Prasad" <sprasad@bivio.net>
To: <linuxppc-dev@ozlabs.org>, <linuxppc-embedded@ozlabs.org>
Subject: Ramdisk Vs NFS
Date: Tue, 24 Apr 2007 20:16:48 -0700	[thread overview]
Message-ID: <D83235F0F3C86D4D889D8B9A0DA8C6D762CA81@corpexc01.corp.networkrobots.com> (raw)

Hi,

What is the primary difference between Ramdisk and NFS with respect to
the wait_queue's?

If I use ramdisk, every thing works fine, but with NFS (or you may read
as 'no ramdisk') kernel/sched.c:__wake_up_common() routines has a
problem. Basically the value of "&q->task_list->next" is out of our
memory range (not between 0xc0000000 and 0xF0000000), and this causes
trouble of accessing non-existing memory.=20

Interesting thing is, this happens much before we even load the ramdisk
drivers.

Appreciate if any one has some insight into this.

Thanks
Siva

                 reply	other threads:[~2007-04-25  3:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=D83235F0F3C86D4D889D8B9A0DA8C6D762CA81@corpexc01.corp.networkrobots.com \
    --to=sprasad@bivio.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.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