From: Robert Read <rread@datarithm.net>
To: linux-kernel@vger.kernel.org
Subject: Re: newbie fodder
Date: Wed, 21 Feb 2001 15:56:18 -0800 [thread overview]
Message-ID: <20010221155618.B8640@tenchi.datarithm.net> (raw)
In-Reply-To: <UTC200102212223.XAA133762.aeb@vlet.cwi.nl>
In-Reply-To: <UTC200102212223.XAA133762.aeb@vlet.cwi.nl>; from Andries.Brouwer@cwi.nl on Wed, Feb 21, 2001 at 11:23:51PM +0100
This looks great, in fact I was working on something similar for
myself. Unfortunately, like all good documentation, it's already
slightly out of date. Just this morning I noticed that as of the
2.4.2-preX, the __make_request function no longer contains this code:
if (!q->plugged)
q->request_fn(q);
I don't know why the change was made, and I have not yet found where
how q->request_fn gets called for non-plugged request queues, but
since this is one of the key steps of the whole process, it will be
great to keep this documentation current.
robert
On Wed, Feb 21, 2001 at 11:23:51PM +0100, Andries.Brouwer@cwi.nl wrote:
> For a beginner I recently wrote a tiny demonstration
> of what the kernel does, given a trivial user program.
> Now that it served its purpose it would be a pity to
> throw it out again, maybe it can be useful to someone else.
>
> See
> http://www.win.tue.nl/~aeb/linux/vfs/trail-1.html
>
> Andries
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-21 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 22:23 newbie fodder Andries.Brouwer
2001-02-21 22:33 ` Eli Carter
2001-02-21 23:56 ` Robert Read [this message]
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=20010221155618.B8640@tenchi.datarithm.net \
--to=rread@datarithm.net \
--cc=linux-kernel@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