public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Samium Gromoff <deepfire@ibe.miee.ru>
Cc: linux-kernel@vger.kernel.org, sct@redhat.com, akpm@digeo.com
Subject: Re: [BIO] request->flags ambiguity
Date: Fri, 27 Jun 2003 13:29:20 +0200	[thread overview]
Message-ID: <20030627112920.GG821@suse.de> (raw)
In-Reply-To: <20030627142829.5aea7015.deepfire@ibe.miee.ru>

On Fri, Jun 27 2003, Samium Gromoff wrote:
> On Fri, 27 Jun 2003 12:48:22 +0200
> Jens Axboe <axboe@suse.de> wrote:
> -- snip --
> > > 	Is it ok to have a possibility of a request with conflicting
> > > 	meanings attached to it?  For example REQ_CMD | REQ_PM_SHUTDOWN
> > > 	| REQ_SPECIAL.
> > 
> > No of course not.
> -- snip --
> > > 	Shouldn`t it make more sense to separate request-type-indicator
> > > 	flags into a separate unambiguous type field, which would take
> > > 	one of the following values: - read/write request - sense query
> > > 	- power control - special request
> > > 
> > > 	And not a currently possible combination of all of them, which
> > > 	seem to be the current situation.
> > 
> > There has been talk of that before, search the archives.
> 
> 	Umm, i`ve tried and failed, couldn`t you share some vague
> 	pointers about the topic or something?

Some pointers here

http://marc.theaimsgroup.com/?l=linux-kernel&m=105482104321668&w=2

-- 
Jens Axboe


      reply	other threads:[~2003-06-27 11:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-27  9:47 [BIO] request->flags ambiguity Samium Gromoff
2003-06-27 10:48 ` Jens Axboe
2003-06-27 10:28   ` Samium Gromoff
2003-06-27 11:29     ` Jens Axboe [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=20030627112920.GG821@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@digeo.com \
    --cc=deepfire@ibe.miee.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    /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