From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Badari Pulavarty <pbadari@us.ibm.com>,
Bill Irwin <bill.irwin@oracle.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] hugetlbfs read() support
Date: Fri, 20 Jul 2007 14:47:31 +1000 [thread overview]
Message-ID: <46A03E63.2080508@yahoo.com.au> (raw)
In-Reply-To: <20070719170759.GE2083@us.ibm.com>
Nishanth Aravamudan wrote:
> On 19.07.2007 [09:58:50 -0700], Andrew Morton wrote:
>
>>On Thu, 19 Jul 2007 08:51:49 -0700 Badari Pulavarty <pbadari@us.ibm.com> wrote:
>>
>>
>>>>>+ }
>>>>>+
>>>>>+ offset += ret;
>>>>>+ retval += ret;
>>>>>+ len -= ret;
>>>>>+ index += offset >> HPAGE_SHIFT;
>>>>>+ offset &= ~HPAGE_MASK;
>>>>>+
>>>>>+ page_cache_release(page);
>>>>>+ if (ret == nr && len)
>>>>>+ continue;
>>>>>+ goto out;
>>>>>+ }
>>>>>+out:
>>>>>+ return retval;
>>>>>+}
>>>>
>>>>This code doesn't have all the ghastly tricks which we deploy to
>>>>handle concurrent truncate.
>>>
>>>Do I need to ? Baaahh!! I don't want to deal with them.
>>
>>Nick, can you think of any serious consequences of a read/truncate
>>race in there? I can't..
>>
>>
>>>All I want is a simple read() to get my oprofile working. Please
>>>advise.
>>
>>Did you consider changing oprofile userspace to read the executable
>>with mmap?
>
>
> It's not actually oprofile's code, though, it's libbfd (used by
> oprofile). And it works fine (presumably) for other binaries.
So... what's the problem with changing it? The fact that it is a
library doesn't really make a difference except that you'll also
help everyone else who links with it.
It won't break backwards compatibility, and it will work on older
kernels...
--
SUSE Labs, Novell Inc.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-07-20 4:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 1:23 Badari Pulavarty
2007-07-19 5:19 ` Andrew Morton
2007-07-19 15:51 ` Badari Pulavarty
2007-07-19 16:58 ` Andrew Morton
2007-07-19 17:07 ` Nishanth Aravamudan
2007-07-19 17:52 ` Bill Irwin
2007-07-31 5:57 ` dean gaudet
2007-07-20 4:47 ` Nick Piggin [this message]
2007-07-23 14:02 ` Nishanth Aravamudan
2007-07-20 4:29 ` Nick Piggin
2007-07-20 21:15 ` Badari Pulavarty
2007-07-20 4:39 ` Nick Piggin
2007-07-20 6:13 ` Nick Piggin
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=46A03E63.2080508@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=bill.irwin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nacc@us.ibm.com \
--cc=pbadari@us.ibm.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