From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 14328] Consistent the size type. New logic to use.
Date: Tue, 6 Oct 2009 08:54:14 GMT [thread overview]
Message-ID: <200910060854.n968sE00004988@demeter.kernel.org> (raw)
In-Reply-To: <bug-14328-11311-V0hAGp6uBxO456/isadD/XN4h3HLQggn@public.gmane.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=14328
Victor Mineev <vik-cfgfcfnPGrx6k2ZkT/Rh8A@public.gmane.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
--- Comment #1 from Victor Mineev <vik-cfgfcfnPGrx6k2ZkT/Rh8A@public.gmane.org> 2009-10-06 08:54:14 ---
Lazy algorithm is the right thing to do. Do user space read a lot better. Let
protect high half of memory region as read/write disabled. So data begin can go
to user space fast soon. And lazy detect of negative size value become true. Is
the kernel do read syncronicly? It is so fantastic to test where is a kvm guest
do the last access.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-06 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 21:23 [Bug 14328] New: Consistent the size type. New logic to use bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
[not found] ` <bug-14328-11311-V0hAGp6uBxO456/isadD/XN4h3HLQggn@public.gmane.org/>
2009-10-06 8:54 ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
2009-11-01 11:00 ` [Bug 14328] " bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
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=200910060854.n968sE00004988@demeter.kernel.org \
--to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).