From: Markus Armbruster <armbru@redhat.com>
To: "Jaya Kumar" <jayakumar.lkml@gmail.com>
Cc: "Jeremy Fitzhardinge" <jeremy@goop.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: "fb-defio: fix page list with concurrent processes"
Date: Tue, 17 Jun 2008 11:31:35 +0200 [thread overview]
Message-ID: <87hcbsmmq0.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <45a44e480806170121s222906cdt23db2d6c394a50a1@mail.gmail.com> (Jaya Kumar's message of "Tue\, 17 Jun 2008 01\:21\:13 -0700")
"Jaya Kumar" <jayakumar.lkml@gmail.com> writes:
> On Tue, Jun 17, 2008 at 12:34 AM, Markus Armbruster <armbru@redhat.com> wrote:
>> "Jaya Kumar" <jayakumar.lkml@gmail.com> writes:
>>
>>> On Mon, Jun 16, 2008 at 3:05 PM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>>>> Your patch "fb-defio: fix page list with concurrent processes" definitely
>>>> seems to help with the suspend/resume problem I had with the Xen pvfb
>>>> device. Is it queued up anywhere? It seems to be a real bugfix, and should
>>>> probably be queued for 2.6.26...
>>>
>>> It isn't currently queued. I had intended to improve its performance
>>> by taking advantage of Andrew's suggestion of using !list_empty on the
>>> page->lru to avoid walking the page list to find the duplicate page,
>>> but I ran into trouble since the page starts off being on the lru
>>> list. I'll try to take a look at doing this next weekend.
>>>
>>> Thanks,
>>> jaya
>>
>> Well, we got a bug that makes the code useless in practice for us, and
>> a fix for it that's not quite as fast as it could be. Which is
>> better, somewhat slow code, or somewhat useless code? I'd like to see
>> the fix merged as soon as possible. You can always improve its
>> performance later.
>>
>
> Ok, I didn't realize there was any time pressure. Keep in mind, I'm
> just a person doing this stuff for fun on weekends not someone under
> commercial pressures. Yup, I've got no problem if the old patch is
> requeued and merged.
>
> Thanks,
> jaya
Hey, it's your own fault! If you wrote useless code in your spare
time, we wouldn't bother you ;->
Seriously, I appreciate your contributions, and I didn't mean to
pressure you. Just to explain why I think it makes sense to merge
your fix now, and performance improvements later.
next prev parent reply other threads:[~2008-06-17 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 22:05 Jeremy Fitzhardinge
2008-06-17 1:11 ` Jaya Kumar
2008-06-17 7:34 ` Markus Armbruster
2008-06-17 8:21 ` Jaya Kumar
2008-06-17 9:31 ` Markus Armbruster [this message]
2008-07-03 21:10 ` Markus Armbruster
2008-07-03 23:44 ` Jaya Kumar
2008-07-07 20:43 ` Markus Armbruster
2008-07-08 0:54 ` Jaya Kumar
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=87hcbsmmq0.fsf@pike.pond.sub.org \
--to=armbru@redhat.com \
--cc=jayakumar.lkml@gmail.com \
--cc=jeremy@goop.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
all inboxes | Powered by JetHome®