linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joel Becker <jlbec@evilplan.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	Ben Myers <bpm@sgi.com>,
	lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-scsi@vger.kernel.org
Subject: Re: [LSF/MM TOPIC][ATTEND] protection information and userspace
Date: Fri, 8 Feb 2013 01:36:01 -0800	[thread overview]
Message-ID: <20130208093558.GA2733@localhost> (raw)
In-Reply-To: <yq1k3qkrl8m.fsf@sermon.lab.mkp.net>

On Thu, Feb 07, 2013 at 02:12:57PM -0500, Martin K. Petersen wrote:
> >>>>> "Joel" == Joel Becker <jlbec@evilplan.org> writes:
> 
> Joel> I'm happy to chat about it.  Unfortunately, like Darrick says,
> Joel> sys_dio() coding hasn't happened.  I do think we're better off
> Joel> with some kind of explicit API than some magic state on the file.
> Joel> I mean, even something like:
> 
> Joel> 	ssize_t write_with_pi(int fd, const void *buf, size_t count,
> Joel> 			      const void *pi, size_t pi_count);
> 
> Joel> It's not as nice as a non-historical API (eg sys_dio), but it also
> Joel> probably plays nicer with buffered I/O.
> 
> Pretty much everyone I have talked to that are interested in explicitly
> attaching PI (as opposed to relying on the kernel doing it) are using
> Linux aio.
> 
> I am not opposed to having more read()/write() like interface as
> well. But I think it's important to cater to the I/O paradigm used by
> the applications interested in this. It's a lot easier to tweak a few
> IOCB fields than it is to rewrite how an application does I/O.

You know I'm not going to argue with this.  I was merely stating that
I'm flexible in how we start :-)

Joel

> 
> -- 
> Martin K. Petersen	Oracle Linux Engineering
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 

"Depend on the rabbit's foot if you will, but remember, it didn't
 help the rabbit."
	- R. E. Shay

			http://www.jlbec.org/
			jlbec@evilplan.org

  reply	other threads:[~2013-02-08  9:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 19:51 [LSF/MM TOPIC][ATTEND] protection information and userspace Ben Myers
2013-02-06 20:24 ` Darrick J. Wong
2013-02-06 20:34   ` Chuck Lever
2013-02-07  9:40     ` Joel Becker
2013-02-07 10:01       ` Darrick J. Wong
2013-02-07 11:27         ` Hannes Reinecke
2013-02-07 12:08           ` Boaz Harrosh
2013-02-07 12:16             ` Boaz Harrosh
2013-02-07 12:33               ` Hannes Reinecke
2013-02-07 12:54                 ` Boaz Harrosh
2013-02-07 12:29             ` Bart Van Assche
2013-02-07 12:47               ` Boaz Harrosh
2013-02-07 16:19             ` Jeff Moyer
2013-02-07 17:27               ` Zach Brown
2013-02-07 17:36                 ` Joel Becker
2013-02-07 21:04                   ` J. Bruce Fields
2013-02-08  9:38                     ` Joel Becker
2013-02-07 19:12       ` Martin K. Petersen
2013-02-08  9:36         ` Joel Becker [this message]
2013-02-07 19:09   ` Martin K. Petersen
2013-02-07 23:45     ` Darrick J. Wong
2013-02-07 23:59       ` Martin K. Petersen
2013-02-07 19:20 ` Martin K. Petersen

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=20130208093558.GA2733@localhost \
    --to=jlbec@evilplan.org \
    --cc=bpm@sgi.com \
    --cc=chuck.lever@oracle.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).