From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: ptb@it.uc3m.es
Cc: Thunder from the hill <thunder@lightweight.ods.org>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: block device/VM question
Date: Tue, 27 Aug 2002 20:40:44 +0200 (MET DST) [thread overview]
Message-ID: <200208271840.g7RIeiH08814@oboe.it.uc3m.es> (raw)
In-Reply-To: From "(env:" "ptb)" at "Aug 27, 2002 08:04:48 pm"
"ago ptb wrote:"
> In dentry_open(), we get a struct file f = get_empty_filp(), and then
> fill out various of its fields with enormously obscure things. And for
> the O_DIRECT flag we seem to do alloc_kiovec(1, &f->f_iobuf).
>
> I feel that the latter is all I want to do, and the question is to what,
> where (I'll clean up on release). Do I do this every time the devices
> _open() function is called? Or just once, and what do I do it to? I
> should do it to the struct file that gets passed into to the driver
> open()? I'll try that. And set the flag.
Well, that was fun! I checked that on entry into the devices
open function, the file->f_iobuf field was null, and then called
alloc_kiovec on it while I set the O_DIRECT flag on file-_f_flags.
The result was that all read/write calls on the device failed
with EINVAL! Whee!
But ioctls worked. Apparently I am supposed to fill out
some more fields of something else with some methods. Hmm. OK.
I'll look. I guess this will be the a_ops field of i_mapping.
Peter
next reply other threads:[~2002-08-27 18:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 18:40 Peter T. Breuer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-29 5:45 Peter T. Breuer
2002-08-28 14:38 Peter T. Breuer
[not found] <Pine.LNX.4.44.0208271118000.3234-100000@hawkeye.luckynet.adm>
2002-08-27 18:04 ` Peter T. Breuer
2002-08-27 19:13 ` Thunder from the hill
2002-08-27 19:28 ` Peter T. Breuer
[not found] <Pine.LNX.4.44.0208271100460.3234-100000@hawkeye.luckynet.adm>
2002-08-27 17:12 ` Peter T. Breuer
[not found] <Pine.LNX.4.44.0208271021020.3234-100000@hawkeye.luckynet.adm>
2002-08-27 16:32 ` Peter T. Breuer
2002-08-27 16:42 ` Thunder from the hill
2002-08-27 16:57 ` Peter T. Breuer
2002-08-27 11:28 Peter T. Breuer
2002-08-27 8:58 Peter T. Breuer
2002-08-27 16:06 ` Thunder from the hill
2002-08-27 16:14 ` Peter T. Breuer
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=200208271840.g7RIeiH08814@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder@lightweight.ods.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
all inboxes | Powered by JetHome®