From: "LA Walsh" <law@sgi.com>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
linux-fsdevel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: RE: address_space: Theory of operation?
Date: Tue, 6 Feb 2001 07:52:55 -0800 [thread overview]
Message-ID: <NBBBJGOOMDFADJDGDCPHKEDPCKAA.law@sgi.com> (raw)
In-Reply-To: <20010206134821.Q849@nightmaster.csn.tu-chemnitz.de>
Also, more widely, any of the new op fields the blk ops, the new inode
fields,
getattr/setattr, etc...descriptions would be "real keen"....:-)
> -----Original Message-----
> From: linux-fsdevel-owner@vger.kernel.org
> [mailto:linux-fsdevel-owner@vger.kernel.org]On Behalf Of Ingo Oeser
> Sent: Tuesday, February 06, 2001 4:48 AM
> To: linux-fsdevel@vger.kernel.org
> Cc: linux-mm@kvack.org
> Subject: address_space: Theory of operation?
>
>
> Hi there,
>
> is there any description of what address_space is supposed to to?
>
> What are the address_space_operations expected to handle?
>
> Sure, I could look into the sources to find out (and I did
> already), but how could I distinguish between a proper
> implementation and a BUG?
>
> I searched the archives already (but using address_space as
> primary keyword, so I wouldn't get renames) without any luck.
>
> So could somebody please point me to some documentation about it
> or comment it, if there is none?
>
> Many thanks!
>
> Regards
>
> Ingo Oeser
> --
> 10.+11.03.2001 - 3. Chemnitzer LinuxTag
<http://www.tu-chemnitz.de/linux/tag>
<<<<<<<<<<<< come and join the fun >>>>>>>>>>>>
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
prev parent reply other threads:[~2001-02-06 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 12:48 Ingo Oeser
2001-02-06 15:48 ` Christoph Hellwig
2001-02-06 15:52 ` LA Walsh [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=NBBBJGOOMDFADJDGDCPHKEDPCKAA.law@sgi.com \
--to=law@sgi.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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