linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tao Ma <tm@tao.ma>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, sfr@canb.auug.org.au,
	linux-fsdevel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
	Tao Ma <boyu.mt@taobao.com>, Andy Whitcroft <apw@canonical.com>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: interims VFS queue
Date: Sun, 30 Oct 2011 15:36:23 +0800	[thread overview]
Message-ID: <4EACFE77.9040807@tao.ma> (raw)
In-Reply-To: <20111029105856.GA6479@infradead.org>

On 10/29/2011 06:58 PM, Christoph Hellwig wrote:
> On Fri, Oct 28, 2011 at 03:09:36PM -0700, Andrew Morton wrote:
>> 1: What happened with Andi's "dio: optimize cache misses in the
>>    submission path"?  (Against which I have checkpatch fixes and
>>    #include linux/prefetch.h, btw)
> 
> It has mostly been merged, including all whitespace fixes and some
> folding.  What is missing is the last two patchees because I don't
> want to put the request_queue caching in until the remaining
> lifetime issues for the request queue are sorted out, and the last
> patch (which would need prefetch.h) depends on it.
> 
>>
>> 2: I'm still sitting on Andy Whitcroft's "readlinkat: ensure we
>>    return ENOENT for the empty pathname for normal lookups" and its
>>    fixup.  I'd marked this as needed-in-3.1.  Help.
> 
> 
> 
>>
>> From: Andy Whitcroft <apw@canonical.com>
>> Subject: readlinkat: ensure we return ENOENT for the empty pathname for normal lookups
>>
>> Since the commit below which added O_PATH support to the *at() calls, the
>> error return for readlink/readlinkat for the empty pathname has switched
>> from ENOENT to EINVAL:
> 
> The fix is defintively required, I'll look over it in a bit more detail
> and will push it with the next round.
> 
>>
>> 3: I'm also sitting on Hans Verkuil's "poll: add
>>    poll_requested_events() function".  This is being merged via the v4l
>>    tree, based on looks-ok-to-akpm.  AFAIK nobody else has looked at
>>    it.  This should be in linux-next via the v4l tree by now, but it
>>    isn't, so something might have gone wrong.
> 
> That was my assumption, too. 
> 
>>
>> 4: I'm still sitting on Steve Rago's "fcntl(F_SETFL): allow setting
>>    of O_SYNC".  I have a comment here that you said it "needs an
>>    audit".  AFAIK nothing has happened.  Should I toss it?
> 
> This also needs all the other bits I mentioned during review.
> 
>> 5: Tao Ma's "fs/direct-io.c: calculate fs_count correctly in
>>    get_more_blocks()" was missed and needs rework as a result of this
>>    merge.  Here's what I now have.  It compiles.
> 
> Tao, can you please resend it against current Linus' tree after making
> sure the upated version is still fine?
OK, I will try to rebase it and do some test against it.

Thanks.
Tao

  parent reply	other threads:[~2011-10-30  7:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28 13:30 interims VFS queue Christoph Hellwig
2011-10-28 18:43 ` Stephen Rothwell
2011-10-28 19:08   ` Linus Torvalds
2011-10-28 19:31     ` Stephen Rothwell
2011-10-28 19:13   ` Stephen Rothwell
2011-10-28 22:09 ` Andrew Morton
2011-10-29 10:58   ` Christoph Hellwig
2011-10-29 11:49     ` caching the request queue was " Andi Kleen
2011-11-02  2:47       ` Vivek Goyal
2011-10-30  7:36     ` Tao Ma [this message]
2011-10-31  7:24     ` [PATCH for 3.2] fs/direct-io.c: Calculate fs_count correctly in get_more_blocks Tao Ma
2011-10-31 18:12       ` Jeff Moyer
2011-11-01  3:31         ` Tao Ma
2011-11-02  2:26         ` [PATCH V2 " Tao Ma
2011-11-02  7:36           ` Christoph Hellwig
2011-11-03  3:21             ` Tao Ma
2011-10-29 13:48   ` interims VFS queue Aneesh Kumar K.V
2011-10-29 14:37     ` Christoph Hellwig
2011-10-30 15:47   ` Hans Verkuil
2011-11-02 13:28 ` interims VFS queue, part2 Christoph Hellwig

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=4EACFE77.9040807@tao.ma \
    --to=tm@tao.ma \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=apw@canonical.com \
    --cc=boyu.mt@taobao.com \
    --cc=hch@infradead.org \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).