From: Thomas Zimmermann <tzimmermann@suse.de>
To: daniel@ffwll.ch, javierm@redhat.com, noralf@tronnes.org,
andriy.shevchenko@linux.intel.com, deller@gmx.de,
bernie@plugable.com, jayalk@intworks.biz
Cc: dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH 0/2] fbdev: Significantly improve performance of fbdefio mmap
Date: Thu, 10 Feb 2022 15:11:09 +0100 [thread overview]
Message-ID: <20220210141111.5231-1-tzimmermann@suse.de> (raw)
Remove the bubble sort from fbdev defered I/O page tracking. Most
drivers only want to know which pages have been written to. The exact
order is not important.
Tested on simpledrm.
Thomas Zimmermann (2):
fbdev/defio: Early-out if page is already enlisted
fbdev: Don't sorting deferred-I/O pages by default
drivers/staging/fbtft/fbtft-core.c | 1 +
drivers/video/fbdev/broadsheetfb.c | 1 +
drivers/video/fbdev/core/fb_defio.c | 38 +++++++++++++++++------------
drivers/video/fbdev/metronomefb.c | 1 +
drivers/video/fbdev/udlfb.c | 1 +
include/linux/fb.h | 1 +
6 files changed, 28 insertions(+), 15 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-10 14:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 14:11 Thomas Zimmermann [this message]
2022-02-10 14:11 ` [PATCH 1/2] fbdev/defio: Early-out if page is already enlisted Thomas Zimmermann
2022-02-10 21:00 ` Sam Ravnborg
2022-02-11 9:12 ` Thomas Zimmermann
2022-02-10 14:11 ` [PATCH 2/2] fbdev: Don't sort deferred-I/O pages by default Thomas Zimmermann
2022-02-10 16:15 ` Andy Shevchenko
2022-02-10 21:16 ` Sam Ravnborg
2022-02-11 7:58 ` Dan Carpenter
2022-02-11 8:25 ` Thomas Zimmermann
2022-02-11 8:21 ` Thomas Zimmermann
2022-02-14 8:05 ` Geert Uytterhoeven
2022-02-14 8:28 ` Thomas Zimmermann
2022-02-14 9:05 ` Geert Uytterhoeven
2022-02-14 13:29 ` Thomas Zimmermann
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=20220210141111.5231-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bernie@plugable.com \
--cc=daniel@ffwll.ch \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=jayalk@intworks.biz \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=noralf@tronnes.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).