public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: ksummit-2008-discuss@lists.linux-foundation.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Current List of Kernel Summit suggested topics from the discuss  list
Date: Fri, 27 Jun 2008 19:18:33 +0200	[thread overview]
Message-ID: <20080627171832.GE20826@kernel.dk> (raw)
In-Reply-To: <1214577710.3394.14.camel@localhost.localdomain>

On Fri, Jun 27 2008, James Bottomley wrote:
>      4. Barriers - Neil Brown
>               * Need to define what semantics filesystems actually want
>               * Need to relate this to what devices and subsystems can
>                 actually provide.

Again? Barriers must be the most persistent topic at the kernel summit,
yet nothing has happened since my initial implementation back in 2001 or
so! :-)

This being a fairly wide and technical topic, I think it's actually
better suited for mailing list discussion for starters.

-- 
Jens Axboe


  parent reply	other threads:[~2008-06-27 17:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 14:41 Current List of Kernel Summit suggested topics from the discuss list James Bottomley
2008-06-27 14:53 ` [Ksummit-2008-discuss] " Arjan van de Ven
2008-06-27 15:09   ` James Bottomley
2008-06-27 15:19     ` Rafael J. Wysocki
2008-06-27 17:35   ` Jesse Barnes
2008-06-27 18:11     ` H. Peter Anvin
2008-06-27 18:23       ` Jesse Barnes
2008-06-27 15:19 ` Christoph Hellwig
2008-06-27 17:18 ` Jens Axboe [this message]
2008-07-03  9:29 ` Arnd Bergmann
2008-07-03 18:27 ` [Ksummit-2008-discuss] " Greg KH
2008-07-03 23:59   ` Stephen Rothwell

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=20080627171832.GE20826@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ksummit-2008-discuss@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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