Re: Time to increase MAXPHYS?

2017-09-15 Thread Warner Losh
On Fri, Sep 15, 2017 at 9:18 AM, Nikolai Lifanov wrote: > On 6/3/17 11:55 PM, Allan Jude wrote: > > On 2017-06-03 22:35, Julian Elischer wrote: > >> On 4/6/17 4:59 am, Colin Percival wrote: > >>> On January 24, 1998, in what was later renumbered to SVN r32724, dyson@ > >>>

Re: Time to increase MAXPHYS?

2017-09-15 Thread Nikolai Lifanov
On 6/3/17 11:55 PM, Allan Jude wrote: > On 2017-06-03 22:35, Julian Elischer wrote: >> On 4/6/17 4:59 am, Colin Percival wrote: >>> On January 24, 1998, in what was later renumbered to SVN r32724, dyson@ >>> wrote: Add better support for larger I/O clusters, including larger physical

Re: Time to increase MAXPHYS?

2017-06-14 Thread Jia-Shiun Li
On Sun, Jun 4, 2017 at 1:33 PM, Warner Losh wrote: > On Sat, Jun 3, 2017 at 2:59 PM, Colin Percival > wrote: > > > On January 24, 1998, in what was later renumbered to SVN r32724, dyson@ > > wrote: > > > Add better support for larger I/O clusters,

Re: Time to increase MAXPHYS?

2017-06-10 Thread Tomoaki AOKI
_ > From: owner-freebsd-curr...@freebsd.org <owner-freebsd-curr...@freebsd.org> > on behalf of Konstantin Belousov <kostik...@gmail.com> > Sent: Sunday, June 4, 2017 4:10:32 AM > To: Warner Losh > Cc: Allan Jude; FreeBSD Current > Subject: Re: Time to increase MAXPHYS? &

Re: Time to increase MAXPHYS?

2017-06-08 Thread Edward Tomasz Napierała
On 0605T1849, Edward Tomasz Napierała wrote: > On 0604T0952, Hans Petter Selasky wrote: > > On 06/04/17 09:39, Tomoaki AOKI wrote: > > > Hi > > > > > > One possibility would be to make it MD build-time OTIONS, > > > defaulting 1M on regular systems and 128k on smaller systems. > > > > > > Of

Re: Time to increase MAXPHYS?

2017-06-08 Thread Edward Tomasz Napierała
Huh, can't say I've tested that. I'll try to look into this. Thanks for the report! On 0608T2046, peter.b...@bsd4all.org wrote: > One area that breaks after changing MAXPHYS from 128K to 1MB is the iscsi > target. I don’t have details, because that server is semi-production and I > reverted

Re: Time to increase MAXPHYS?

2017-06-08 Thread peter . blok
One area that breaks after changing MAXPHYS from 128K to 1MB is the iscsi target. I don’t have details, because that server is semi-production and I reverted it back ASAP > On 5 Jun 2017, at 19:49, Edward Tomasz Napierała wrote: > > On 0604T0952, Hans Petter Selasky wrote:

Re: Time to increase MAXPHYS?

2017-06-05 Thread Edward Tomasz Napierała
On 0604T0952, Hans Petter Selasky wrote: > On 06/04/17 09:39, Tomoaki AOKI wrote: > > Hi > > > > One possibility would be to make it MD build-time OTIONS, > > defaulting 1M on regular systems and 128k on smaller systems. > > > > Of course I guess making it a tunable (or sysctl) would be best, >

Re: Time to increase MAXPHYS?

2017-06-05 Thread Kenneth D. Merry
On Sun, Jun 04, 2017 at 09:52:36 +0200, Hans Petter Selasky wrote: > On 06/04/17 09:39, Tomoaki AOKI wrote: > > Hi > > > > One possibility would be to make it MD build-time OTIONS, > > defaulting 1M on regular systems and 128k on smaller systems. > > > > Of course I guess making it a tunable (or

Re: Time to increase MAXPHYS?

2017-06-04 Thread Slawa Olhovchenkov
On Sat, Jun 03, 2017 at 11:49:01PM -0600, Warner Losh wrote: > > Netflix runs MAXPHYS of 8MB. There's issues with something this big, to be > > sure, especially on memory limited systems. Lots of hardware can't do this > > big an I/O, and some drivers can't cope, even if the underlying hardware >

Re: Time to increase MAXPHYS?

2017-06-04 Thread Slawa Olhovchenkov
On Sat, Jun 03, 2017 at 11:55:51PM -0400, Allan Jude wrote: > On 2017-06-03 22:35, Julian Elischer wrote: > > On 4/6/17 4:59 am, Colin Percival wrote: > >> On January 24, 1998, in what was later renumbered to SVN r32724, dyson@ > >> wrote: > >>> Add better support for larger I/O clusters,

Re: Time to increase MAXPHYS?

2017-06-04 Thread Rick Macklem
reebsd.org <owner-freebsd-curr...@freebsd.org> on behalf of Konstantin Belousov <kostik...@gmail.com> Sent: Sunday, June 4, 2017 4:10:32 AM To: Warner Losh Cc: Allan Jude; FreeBSD Current Subject: Re: Time to increase MAXPHYS? On Sat, Jun 03, 2017 at 11:28:23PM -0600, Warner Losh

Re: Time to increase MAXPHYS?

2017-06-04 Thread Tomoaki AOKI
On Sun, 4 Jun 2017 09:52:36 +0200 Hans Petter Selasky wrote: > On 06/04/17 09:39, Tomoaki AOKI wrote: > > Hi > > > > One possibility would be to make it MD build-time OTIONS, > > defaulting 1M on regular systems and 128k on smaller systems. > > > > Of course I guess making it

Re: Time to increase MAXPHYS?

2017-06-04 Thread Konstantin Belousov
On Sat, Jun 03, 2017 at 11:28:23PM -0600, Warner Losh wrote: > On Sat, Jun 3, 2017 at 9:55 PM, Allan Jude wrote: > > > On 2017-06-03 22:35, Julian Elischer wrote: > > > On 4/6/17 4:59 am, Colin Percival wrote: > > >> On January 24, 1998, in what was later renumbered to SVN

Re: Time to increase MAXPHYS?

2017-06-04 Thread Hans Petter Selasky
On 06/04/17 09:39, Tomoaki AOKI wrote: Hi One possibility would be to make it MD build-time OTIONS, defaulting 1M on regular systems and 128k on smaller systems. Of course I guess making it a tunable (or sysctl) would be best, though. Hi, A tunable sysctl would be fine, but beware that

Re: Time to increase MAXPHYS?

2017-06-04 Thread Tomoaki AOKI
Hi One possibility would be to make it MD build-time OTIONS, defaulting 1M on regular systems and 128k on smaller systems. Of course I guess making it a tunable (or sysctl) would be best, though. On Sat, 3 Jun 2017 23:49:01 -0600 Warner Losh wrote: > On Sat, Jun 3, 2017 at

Re: Time to increase MAXPHYS?

2017-06-03 Thread Warner Losh
On Sat, Jun 3, 2017 at 11:28 PM, Warner Losh wrote: > > > On Sat, Jun 3, 2017 at 9:55 PM, Allan Jude wrote: > >> On 2017-06-03 22:35, Julian Elischer wrote: >> > On 4/6/17 4:59 am, Colin Percival wrote: >> >> On January 24, 1998, in what was later

Re: Time to increase MAXPHYS?

2017-06-03 Thread Warner Losh
On Sat, Jun 3, 2017 at 2:59 PM, Colin Percival wrote: > On January 24, 1998, in what was later renumbered to SVN r32724, dyson@ > wrote: > > Add better support for larger I/O clusters, including larger physical > > I/O. The support is not mature yet, and some of the

Re: Time to increase MAXPHYS?

2017-06-03 Thread Warner Losh
On Sat, Jun 3, 2017 at 9:55 PM, Allan Jude wrote: > On 2017-06-03 22:35, Julian Elischer wrote: > > On 4/6/17 4:59 am, Colin Percival wrote: > >> On January 24, 1998, in what was later renumbered to SVN r32724, dyson@ > >> wrote: > >>> Add better support for larger I/O

Re: Time to increase MAXPHYS?

2017-06-03 Thread Allan Jude
On 2017-06-03 22:35, Julian Elischer wrote: > On 4/6/17 4:59 am, Colin Percival wrote: >> On January 24, 1998, in what was later renumbered to SVN r32724, dyson@ >> wrote: >>> Add better support for larger I/O clusters, including larger physical >>> I/O. The support is not mature yet, and some of

Re: Time to increase MAXPHYS?

2017-06-03 Thread Julian Elischer
On 4/6/17 4:59 am, Colin Percival wrote: On January 24, 1998, in what was later renumbered to SVN r32724, dyson@ wrote: Add better support for larger I/O clusters, including larger physical I/O. The support is not mature yet, and some of the underlying implementation needs help. However,

Time to increase MAXPHYS?

2017-06-03 Thread Colin Percival
On January 24, 1998, in what was later renumbered to SVN r32724, dyson@ wrote: > Add better support for larger I/O clusters, including larger physical > I/O. The support is not mature yet, and some of the underlying implementation > needs help. However, support does exist for IDE devices now.