On Fri, Aug 10, 2018 at 5:30 PM, Erich Dollansky <
freebsd.ed.li...@sumeritec.com> wrote:
> Hi,
>
> On Fri, 10 Aug 2018 07:53:19 -0600
> Warner Losh wrote:
>
> > On Thu, Aug 9, 2018 at 11:51 PM, Erich Dollansky <
> > freebsd.ed.li...@sumeritec.com> wrote:
> >
> > > On Fri, 10 Aug 2018 12:40:48
Hi,
On Fri, 10 Aug 2018 07:53:19 -0600
Warner Losh wrote:
> On Thu, Aug 9, 2018 at 11:51 PM, Erich Dollansky <
> freebsd.ed.li...@sumeritec.com> wrote:
>
> > On Fri, 10 Aug 2018 12:40:48 +0800
> > blubee blubeeme wrote:
> >
> > >
> > > What about the architecture name is it recommended to
Hello,
This is probably a driver issue. The only way I could get sr-iov
working with the ix driver is compiling the driver provided
by Intel and loading it before boot. [1] for more details and [2]
for the driver. Have not tested the latest version and only
tested this on CURRENT. Also, there
On Thu, Aug 09, 2018 at 08:38:50PM +, Rick Macklem wrote:
> >BTW, does NFS server use extended attributes ? What for ? Can you, please,
> >point out the code which does this ?
> For the pNFS service, there are two system namespace extended attributes for
> each file stored on the service.
>
On 8/10/18 9:52 AM, Ultima wrote:
Hello,
This is probably a driver issue. The only way I could get sr-iov
working with the ix driver is compiling the driver provided
by Intel and loading it before boot. [1] for more details and [2]
for the driver. Have not tested the latest version and only
On 8/10/18 8:30 AM, Ryan Stone wrote:
How many VFs are you trying to create? Getting ENOSPC either
indicates that you tried to allocate more VFs than the hardware
supports, or the system could not allocate enough MMIO space for the
VFs.
Hi Ryan,
I was attempting to create a single VF.
How many VFs are you trying to create? Getting ENOSPC either
indicates that you tried to allocate more VFs than the hardware
supports, or the system could not allocate enough MMIO space for the
VFs.
On Thu, Aug 9, 2018 at 10:41 PM Pete Wright wrote:
>
> hello,
>
> i have a newly provisioned VPS
On Fri, Aug 10, 2018 at 9:53 PM Warner Losh wrote:
>
>
> On Thu, Aug 9, 2018 at 11:51 PM, Erich Dollansky <
> freebsd.ed.li...@sumeritec.com> wrote:
>
>> Hi,
>>
>> On Fri, 10 Aug 2018 12:40:48 +0800
>> blubee blubeeme wrote:
>>
>> > On Fri, Aug 10, 2018 at 8:28 AM Erich Dollansky <
>> >
On Thu, Aug 9, 2018 at 11:51 PM, Erich Dollansky <
freebsd.ed.li...@sumeritec.com> wrote:
> Hi,
>
> On Fri, 10 Aug 2018 12:40:48 +0800
> blubee blubeeme wrote:
>
> > On Fri, Aug 10, 2018 at 8:28 AM Erich Dollansky <
> > freebsd.ed.li...@sumeritec.com> wrote:
> >
> > > Hi,
> > >
> > > On Fri, 10
Konstantin Belousov wrote:
>On Thu, Aug 09, 2018 at 08:38:50PM +, Rick Macklem wrote:
>> I did notice that my code locks the vnode first and then calls
>> vn_start_write()
>> for the vn_extattr_set() calls, whereas the syscall code locks the vnode
>> after the vn_start_write() call.
>>
>>
On 10.08.18 04:38, Pete Wright wrote:
> hello,
>
> i have a newly provisioned VPS system from Vultr which comes stock with
> a 10Gbe ix interface:
>
> ix0@pci0:1:0:0: class=0x02 card=0x082315d9 chip=0x15578086 rev=0x01
> hdr=0x00
> vendor = 'Intel Corporation'
> device =
On Thu, Aug 09, 2018 at 08:38:50PM +, Rick Macklem wrote:
> I did notice that my code locks the vnode first and then calls
> vn_start_write()
> for the vn_extattr_set() calls, whereas the syscall code locks the vnode
> after the vn_start_write() call.
>
> Does that matter?
Yes, it matter.
12 matches
Mail list logo