mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: Thunder from the hill <thunder@lightweight.ods.org>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: block device/VM question
Date: Tue, 27 Aug 2002 19:12:24 +0200 (MET DST)	[thread overview]
Message-ID: <200208271712.g7RHCOn00898@oboe.it.uc3m.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0208271100460.3234-100000@hawkeye.luckynet.adm> from Thunder from the hill at "Aug 27, 2002 11:04:23 am"

"A month of sundays ago Thunder from the hill wrote:"
> On Tue, 27 Aug 2002, Peter T. Breuer wrote:
> > You mean do a syscall with flags O_DIRECT from within the driver?
> > I don't like syscalsl from kernel code, but if you say so, I'll think
> > about it.
> 
> Not exactly, but it's a starting point. See how.

I think you're directing my attention to how to get to the inode of the
special device file. That's OK. I can get to that with no hassle. Once
there I can do whatever the sysopen with O_DIRECT does.

> <URL:ftp://ftp.es.kernel.org/pub/linux/docs/manpages/man-pages-1.53.tar.bz2>
> 
> Contains lots of the useful stuff.

I'm sure :-). But until it gets packaged for debian I don't touch :-/.

> > suggesting that it depends on the mode of access to the device? That I
> > can't control - I simply want ALL accesses to not be cached.
> 
> That's a word, and confirms the O_DIRECT interface. However, that still 
> doesn't enable me to tell you what exact implementation you'll need. Do 
> you understand my point?

Evidently not.  You must be saying that there are two possible
implementations, and that it is up to me to choose one that I like.
That's nice, but I would like to have the possibilities to choose from
in front of me! While we know schoedinger's cat may only exist or not
exist, it is only possible to say which of the two I prefer once I
have seen at least one of them :-).

Peter

       reply	other threads:[~2002-08-27 17:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0208271100460.3234-100000@hawkeye.luckynet.adm>
2002-08-27 17:12 ` Peter T. Breuer [this message]
2002-08-29  5:45 Peter T. Breuer
  -- strict thread matches above, loose matches on Subject: below --
2002-08-28 14:38 Peter T. Breuer
2002-08-27 18:40 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.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=200208271712.g7RHCOn00898@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®