All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "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 14:54:13 +0200	[thread overview]
Message-ID: <5113A3F5.2050908@panasas.com> (raw)
In-Reply-To: <51139F33.90307@suse.de>

On 02/07/2013 02:33 PM, Hannes Reinecke wrote:
> On 02/07/2013 01:16 PM, Boaz Harrosh wrote:
>> (Again libaio should be changed in concert with Kernel's new API, and we
>>   can sacrifice old user-mode performance, with a COMPAT layer. Distro
>>   maintainers should consider replacing libaio, together with the new
>>   Kernel, so it is only those that do their own mix-and-match, who can
>>   fix that mismatch too)
>>
> And while we're at it, I still would _love_ to connect aio_cancel() 
> and blk_abort_request().
> 
> That way we could sensibly abort an I/O and get out of the darn 'D' 
> state.
> 

Yes!! Thanks. It is very interesting how the socket side of the world
had it correct for ages, and the same "fd" object on disks is second grade
citizen in UNIX land. (Anybody voting for epoll on async disk IO? )

Thanks Hannes yes that too. And wait_interuptable() too, at couple of
places, will need some serious error handling audit for that.

> Cheers,
> 
> Hannes
> 

Boaz


WARNING: multiple messages have this Message-ID (diff)
From: Boaz Harrosh <bharrosh@panasas.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "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 14:54:13 +0200	[thread overview]
Message-ID: <5113A3F5.2050908@panasas.com> (raw)
In-Reply-To: <51139F33.90307@suse.de>

On 02/07/2013 02:33 PM, Hannes Reinecke wrote:
> On 02/07/2013 01:16 PM, Boaz Harrosh wrote:
>> (Again libaio should be changed in concert with Kernel's new API, and we
>>   can sacrifice old user-mode performance, with a COMPAT layer. Distro
>>   maintainers should consider replacing libaio, together with the new
>>   Kernel, so it is only those that do their own mix-and-match, who can
>>   fix that mismatch too)
>>
> And while we're at it, I still would _love_ to connect aio_cancel() 
> and blk_abort_request().
> 
> That way we could sensibly abort an I/O and get out of the darn 'D' 
> state.
> 

Yes!! Thanks. It is very interesting how the socket side of the world
had it correct for ages, and the same "fd" object on disks is second grade
citizen in UNIX land. (Anybody voting for epoll on async disk IO? )

Thanks Hannes yes that too. And wait_interuptable() too, at couple of
places, will need some serious error handling audit for that.

> Cheers,
> 
> Hannes
> 

Boaz


  reply	other threads:[~2013-02-07 12:55 UTC|newest]

Thread overview: 28+ 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:08             ` Boaz Harrosh
2013-02-07 12:16             ` Boaz Harrosh
2013-02-07 12:16               ` Boaz Harrosh
2013-02-07 12:33               ` Hannes Reinecke
2013-02-07 12:54                 ` Boaz Harrosh [this message]
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 12:47                 ` Boaz Harrosh
2013-02-07 16:19             ` Jeff Moyer
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
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=5113A3F5.2050908@panasas.com \
    --to=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.