From: Brad Hards <bhards@bigpond.net.au>
To: linux-hotplug@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: hotplugging to deal with firmware download
Date: Sun, 02 Jun 2002 22:21:46 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102305666231267@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102297360623547@msgid-missing>
On Sun, 2 Jun 2002 15:50, Oliver Neukum wrote:
> Am Sonntag, 2. Juni 2002 13:11 schrieb Brad Hards:
> > On Mon, 3 Jun 2002 00:44, Oliver Neukum wrote:
> > > Am Sonntag, 2. Juni 2002 01:16 schrieben Sie:
> > > > On Sun, 2 Jun 2002 02:07, Oliver Neukum wrote:
> > > > > The problem is that this cannot simply work, because a filesystem
> > > > > may be mounted by nfs.
> > > >
> > > > How is this a problem? You simply need to bring the driver up before
> > > > you remount the nfs filesystem. If you assume that your firmware is
> > > > on that filesystem, then you couldn't have mounted it in the first
> > > > place.
> > > >
> > > > What am I missing here?
> > >
> > > Paging. As soon as user space is running, dirty pages may be written
> > > out And in order to run a user space firmware loader, user space must
> > > be functional, or am I overlooking something?
> >
> > The software support option requires swap to store to, right? That had
> > better be on a local disk, or it doesn't matter whether the firmware is
> > in userspace or not. Realistically, swap over a network block device
> > isn't a problem worth trying to solve.
>
> Not only swap, but any file opened for writing may be written to
> if you allocate memory.
If a file is opened for writing, it doesn't matter whether you allocate memory
or not, it still may be written to. Sync, journalling, that process dirtying
more pages, whatever.
--
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2002-06-02 22:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 23:16 [linux-usb-devel] Re: hotplugging to deal with firmware download Brad Hards
2002-06-02 5:50 ` Oliver Neukum
2002-06-02 8:19 ` Oliver Neukum
2002-06-02 11:11 ` Brad Hards
2002-06-02 17:16 ` David Brownell
2002-06-02 21:59 ` Oliver Neukum
2002-06-02 22:21 ` Brad Hards [this message]
2002-06-03 4:18 ` Oliver Neukum
2002-06-03 17:52 ` Greg KH
2002-06-03 21:00 ` Oliver Neukum
2002-06-03 21:55 ` Greg KH
2002-06-03 22:02 ` David Brownell
2002-06-03 22:26 ` Oliver Neukum
2002-06-03 22:35 ` Greg KH
2002-06-03 22:37 ` Greg KH
2002-06-03 22:48 ` Oliver Neukum
2002-06-03 22:58 ` Oliver Neukum
2002-06-03 23:05 ` Greg KH
2002-06-03 23:30 ` Oliver Neukum
2002-06-03 23:40 ` Greg KH
2002-06-04 8:06 ` Oliver Neukum
2002-06-04 19:32 ` David Brownell
2002-06-04 19:44 ` David Brownell
2002-06-05 11:45 ` Oliver Neukum
2002-06-05 14:19 ` David Brownell
2002-06-05 14:32 ` Oliver Neukum
2002-06-05 14:54 ` David Brownell
2002-06-05 21:48 ` Oliver Neukum
2002-06-06 0:25 ` David Brownell
2002-06-06 9:04 ` Andries.Brouwer
2002-06-06 12:54 ` Oliver Neukum
2002-06-06 14:55 ` Oliver Neukum
2002-06-06 17:16 ` David Brownell
2002-06-06 19:19 ` Andries.Brouwer
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=marc-linux-hotplug-102305666231267@msgid-missing \
--to=bhards@bigpond.net.au \
--cc=linux-hotplug@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.