From: Joel Becker <jlbec@evilplan.org>
To: Zach Brown <zab@redhat.com>
Cc: Jeff Moyer <jmoyer@redhat.com>,
Boaz Harrosh <bharrosh@panasas.com>,
Hannes Reinecke <hare@suse.de>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Chuck Lever <chuck.lever@oracle.com>, Ben Myers <bpm@sgi.com>,
lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Subject: Re: [LSF/MM TOPIC][ATTEND] protection information and userspace
Date: Thu, 7 Feb 2013 09:36:39 -0800 [thread overview]
Message-ID: <20130207173639.GB29575@localhost> (raw)
In-Reply-To: <20130207172735.GR14246@lenny.home.zabbo.net>
Dear LSF committee,
I'd like to explicitly request attendance for this discussion
:-)
Joel
On Thu, Feb 07, 2013 at 09:27:35AM -0800, Zach Brown wrote:
> On Thu, Feb 07, 2013 at 11:19:59AM -0500, Jeff Moyer wrote:
> > Boaz Harrosh <bharrosh@panasas.com> writes:
> > >>
> > >> For aio we just need to add additional fields to an existing structure.
> > >>
> > >> So yeah, I'd be interested in that discussion as well.
> >
> > Sure, it's easy to start there, but then you eventually end up having to
> > add a non-aio interface as well. Let's not take the latter off the
> > table.
>
> I agree that a sync variant should't be ignored, but needing a sync
> interface with PI arguments also shouldn't get in the way of adding
> support to the aio+dio path. Simply because it's what people use :/.
>
> > I'm not sure how that's directly related to aio, but ok. If we're going
> > to rewrite the aio code, I think Zach's acall would be a good start, at
> > least on the API front:
> > http://lwn.net/Articles/316806/
>
> Yeah, I'm happy to chat about this stuff if people are interested. I
> think I'd do things differently today than what was done in that aged
> acall prototype.
>
> - z
> --
> 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
--
"You can get more with a kind word and a gun than you can with
a kind word alone."
- Al Capone
http://www.jlbec.org/
jlbec@evilplan.org
next prev parent reply other threads:[~2013-02-07 17: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 [this message]
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
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=20130207173639.GB29575@localhost \
--to=jlbec@evilplan.org \
--cc=bharrosh@panasas.com \
--cc=bpm@sgi.com \
--cc=chuck.lever@oracle.com \
--cc=darrick.wong@oracle.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=jmoyer@redhat.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 \
--cc=zab@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;
as well as URLs for NNTP newsgroup(s).