search for: 6.1mpps

Displaying 20 results from an estimated 36 matches for "6.1mpps".

[RFC PATCH V3 0/5] Hi:
2019 Jan 07
2
[RFC PATCH V3 0/5] Hi:
On 2019/1/3 ??4:47, Michael S. Tsirkin wrote: > On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote: >> This series tries to access virtqueue metadata through kernel virtual >> address instead of copy_user() friends since they had too much >> overheads like checks, spec barriers or even hardware feature >> toggling. > Will review, thanks! > One questions
[RFC PATCH V3 0/5] Hi:
2019 Jan 07
2
[RFC PATCH V3 0/5] Hi:
On 2019/1/3 ??4:47, Michael S. Tsirkin wrote: > On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote: >> This series tries to access virtqueue metadata through kernel virtual >> address instead of copy_user() friends since they had too much >> overheads like checks, spec barriers or even hardware feature >> toggling. > Will review, thanks! > One questions
[RFC PATCH V3 0/5] Hi:
2019 Jan 07
3
[RFC PATCH V3 0/5] Hi:
On 2019/1/7 ??11:28, Michael S. Tsirkin wrote: > On Mon, Jan 07, 2019 at 10:19:03AM +0800, Jason Wang wrote: >> On 2019/1/3 ??4:47, Michael S. Tsirkin wrote: >>> On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote: >>>> This series tries to access virtqueue metadata through kernel virtual >>>> address instead of copy_user() friends since they had
[RFC PATCH V3 0/5] Hi:
2019 Jan 07
3
[RFC PATCH V3 0/5] Hi:
On 2019/1/7 ??11:28, Michael S. Tsirkin wrote: > On Mon, Jan 07, 2019 at 10:19:03AM +0800, Jason Wang wrote: >> On 2019/1/3 ??4:47, Michael S. Tsirkin wrote: >>> On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote: >>>> This series tries to access virtqueue metadata through kernel virtual >>>> address instead of copy_user() friends since they had
[RFC PATCH V3 0/5] Hi:
2019 Jan 07
0
[RFC PATCH V3 0/5] Hi:
On Mon, Jan 07, 2019 at 11:53:41AM +0800, Jason Wang wrote: > > On 2019/1/7 ??11:28, Michael S. Tsirkin wrote: > > On Mon, Jan 07, 2019 at 10:19:03AM +0800, Jason Wang wrote: > > > On 2019/1/3 ??4:47, Michael S. Tsirkin wrote: > > > > On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote: > > > > > This series tries to access virtqueue metadata
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 26
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Wed, Dec 26, 2018 at 11:57:32AM +0800, Jason Wang wrote: > > On 2018/12/25 ??8:50, Michael S. Tsirkin wrote: > > On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote: > > > On 2018/12/25 ??2:10, Michael S. Tsirkin wrote: > > > > On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote: > > > > > On 2018/12/14 ??8:36, Michael S. Tsirkin
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 26
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Wed, Dec 26, 2018 at 11:57:32AM +0800, Jason Wang wrote: > > On 2018/12/25 ??8:50, Michael S. Tsirkin wrote: > > On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote: > > > On 2018/12/25 ??2:10, Michael S. Tsirkin wrote: > > > > On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote: > > > > > On 2018/12/14 ??8:36, Michael S. Tsirkin
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 30
1
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Thu, Dec 27, 2018 at 05:39:21PM +0800, Jason Wang wrote: > > On 2018/12/26 ??11:02, Michael S. Tsirkin wrote: > > On Wed, Dec 26, 2018 at 11:57:32AM +0800, Jason Wang wrote: > > > On 2018/12/25 ??8:50, Michael S. Tsirkin wrote: > > > > On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote: > > > > > On 2018/12/25 ??2:10, Michael S. Tsirkin
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 25
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote: > > On 2018/12/25 ??2:10, Michael S. Tsirkin wrote: > > On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote: > > > On 2018/12/14 ??8:36, Michael S. Tsirkin wrote: > > > > On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote: > > > > > On 2018/12/13 ??11:44, Michael S. Tsirkin
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 25
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote: > > On 2018/12/25 ??2:10, Michael S. Tsirkin wrote: > > On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote: > > > On 2018/12/14 ??8:36, Michael S. Tsirkin wrote: > > > > On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote: > > > > > On 2018/12/13 ??11:44, Michael S. Tsirkin
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 14
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote: > > On 2018/12/13 ??11:44, Michael S. Tsirkin wrote: > > On Thu, Dec 13, 2018 at 06:10:22PM +0800, Jason Wang wrote: > > > It was noticed that the copy_user() friends that was used to access > > > virtqueue metdata tends to be very expensive for dataplane > > > implementation like vhost since it
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 14
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote: > > On 2018/12/13 ??11:44, Michael S. Tsirkin wrote: > > On Thu, Dec 13, 2018 at 06:10:22PM +0800, Jason Wang wrote: > > > It was noticed that the copy_user() friends that was used to access > > > virtqueue metdata tends to be very expensive for dataplane > > > implementation like vhost since it
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 27
0
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On 2018/12/26 ??11:02, Michael S. Tsirkin wrote: > On Wed, Dec 26, 2018 at 11:57:32AM +0800, Jason Wang wrote: >> On 2018/12/25 ??8:50, Michael S. Tsirkin wrote: >>> On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote: >>>> On 2018/12/25 ??2:10, Michael S. Tsirkin wrote: >>>>> On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote:
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 26
0
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On 2018/12/25 ??8:50, Michael S. Tsirkin wrote: > On Tue, Dec 25, 2018 at 06:05:25PM +0800, Jason Wang wrote: >> On 2018/12/25 ??2:10, Michael S. Tsirkin wrote: >>> On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote: >>>> On 2018/12/14 ??8:36, Michael S. Tsirkin wrote: >>>>> On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote:
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 13
5
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Thu, Dec 13, 2018 at 06:10:22PM +0800, Jason Wang wrote: > It was noticed that the copy_user() friends that was used to access > virtqueue metdata tends to be very expensive for dataplane > implementation like vhost since it involves lots of software check, > speculation barrier, hardware feature toggling (e.g SMAP). The > extra cost will be more obvious when transferring small
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 13
5
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Thu, Dec 13, 2018 at 06:10:22PM +0800, Jason Wang wrote: > It was noticed that the copy_user() friends that was used to access > virtqueue metdata tends to be very expensive for dataplane > implementation like vhost since it involves lots of software check, > speculation barrier, hardware feature toggling (e.g SMAP). The > extra cost will be more obvious when transferring small
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 24
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote: > > On 2018/12/14 ??8:36, Michael S. Tsirkin wrote: > > On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote: > > > On 2018/12/13 ??11:44, Michael S. Tsirkin wrote: > > > > On Thu, Dec 13, 2018 at 06:10:22PM +0800, Jason Wang wrote: > > > > > It was noticed that the copy_user()
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 24
2
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On Mon, Dec 24, 2018 at 03:53:16PM +0800, Jason Wang wrote: > > On 2018/12/14 ??8:36, Michael S. Tsirkin wrote: > > On Fri, Dec 14, 2018 at 11:57:35AM +0800, Jason Wang wrote: > > > On 2018/12/13 ??11:44, Michael S. Tsirkin wrote: > > > > On Thu, Dec 13, 2018 at 06:10:22PM +0800, Jason Wang wrote: > > > > > It was noticed that the copy_user()
[RFC PATCH V3 0/5] Hi:
2019 Jan 07
0
[RFC PATCH V3 0/5] Hi:
On Mon, Jan 07, 2019 at 10:19:03AM +0800, Jason Wang wrote: > > On 2019/1/3 ??4:47, Michael S. Tsirkin wrote: > > On Sat, Dec 29, 2018 at 08:46:51PM +0800, Jason Wang wrote: > > > This series tries to access virtqueue metadata through kernel virtual > > > address instead of copy_user() friends since they had too much > > > overheads like checks, spec
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
2018 Dec 14
0
[PATCH net-next 3/3] vhost: access vq metadata through kernel virtual address
On 2018/12/13 ??11:44, Michael S. Tsirkin wrote: > On Thu, Dec 13, 2018 at 06:10:22PM +0800, Jason Wang wrote: >> It was noticed that the copy_user() friends that was used to access >> virtqueue metdata tends to be very expensive for dataplane >> implementation like vhost since it involves lots of software check, >> speculation barrier, hardware feature toggling (e.g